This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-26
Channels
- # announcements (1)
- # babashka (6)
- # beginners (12)
- # biff (39)
- # calva (4)
- # cider (5)
- # clj-commons (1)
- # clj-yaml (9)
- # clojure (42)
- # clojure-conj (1)
- # clojure-europe (8)
- # clojurescript-ios (1)
- # clr (1)
- # conjure (7)
- # data-science (1)
- # datalevin (9)
- # emacs (3)
- # helix (1)
- # honeysql (11)
- # hyperfiddle (60)
- # introduce-yourself (1)
- # lsp (26)
- # music (1)
- # off-topic (1)
- # pathom (2)
- # polylith (3)
- # releases (1)
- # sci (1)
- # scittle (21)
- # shadow-cljs (57)
- # spacemacs (3)
- # xtdb (38)
Probably a small crowd but for anyone that uses neovim with VS Code and has had problems with paredit, I some time this past week implementing paredit in Lua that using the treesitter API. The linked gist (which will become a proper repo) implements slurp, barf, split, splice, next/prev (like zipper), wrap, kill, yank, and swap. As long as you have treesitter setup, the code can be placed on your runtime path and work. https://gist.github.com/noprompt/176883f76e7051909a16438c357438dd
4Also, this implementation will work for other languages too, not just Clojure. Excluding splice and split, many of these operations will just work for other languages. So far I’ve tested them on VimL and Lua.
Bookmarked for the next time I try out Calva again. Not having good vim+paredit support in VSCode is one reason I could not justify giving up my evil-emacs setup.
@U05476190 Same here. I started using VS Code for everything other than Clojure because Emacs' paredit was flawless.