This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-12
Channels
- # babashka (4)
- # beginners (49)
- # biff (17)
- # calva (12)
- # cider (5)
- # clojure-czech (1)
- # clojure-europe (3)
- # clojure-norway (3)
- # core-logic (1)
- # cursive (4)
- # data-science (2)
- # datalevin (7)
- # emacs (1)
- # events (6)
- # fulcro (11)
- # helix (7)
- # hyperfiddle (30)
- # lsp (4)
- # podcasts-discuss (1)
- # practicalli (4)
- # releases (1)
- # remote-jobs (7)
- # ring (6)
- # spacemacs (4)
- # tools-deps (5)
Anyone else seeing clojure-lsp failing to start in some projects with latest VS Code? If I downgrade to latest version, clojure-lsp starts fine.
clojure-lsp latest. I haven’t tried with something earlier. I should probably check Calva ans clojure-lsp logs first, before deciding how to proceed. I think it could be the latest patch of VS Code, even, 1.84.2, because I upgraded to that one today. Will now try with 1.84.1.
And now I can’t reproduce with latest VS Code. wtf. I’ll pause investigating and pick it up if I see it again.
I noticed that my Calva extension activates when I open a Scheme source file, and it looks like there are a couple places in the Calva source that suggest that Scheme and (Common?) Lisp also work with Calva (https://github.com/BetterThanTomorrow/calva/blob/3f0a345d22302a7bafa944dc237356df7cf609cf/src/paredit/extension.ts#L21 and https://github.com/BetterThanTomorrow/calva/blob/3f0a345d22302a7bafa944dc237356df7cf609cf/docs/site/customizing.md?plain=1#L170). But there aren’t actually any plans to make Calva work with non-Clojure Lisps, right?
No plans, correct. The association is to make Paredit available for lisps in general. It used to be that Calva Paredit was the best implementation for those. Not sure how that holds up today.
Based on a quick experiment activating Calva v2.0.395 and trying out paredit commands, it doesn’t seem to work at all anymore. (That’s really too bad – I love Calva’s paredit, and it’d be great to be able to use it with the other Lisp dialects I’ve started exploring lately.) Would you be interested in a pull request to either get it working again or (more likely) to remove the traces of Scheme and Lisp support? Also, it seems like Calva doesn’t always auto-activate when I open a Scheme (actually Racket) file. I can’t seem to nail down what exactly makes it activate. 🤷
You are very welcome to have a look at it! I think we do not need to auto-associate file extensions to non-Clojure-related files. That is something Scheme users can do if they find that Calva Paredit is better than no structural editor for them.
So, maybe we could start there? The keybindings checks are ok to leave in place, since they would only be in effect when Calva is active.
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.395
• https://github.com/BetterThanTomorrow/calva/issues/2343
In addition to making Calva happy to connect with #squint’s nrepl client (only for connect so far, jack-in will be added on demand) this version also is using nrepl eval op better. Should make Calva behave better when you evaluate a form without having loaded the file first.