calva 2022-05-23 | Slack Archive

maxt06:05:52

One minor thing that annoys me in Calva is the default comment-snippet that gets in my way when I try to add a comment block. I'll type (comment⏎ and I'll get double parenthesis. Is this an issue others experience too?

➕ 1

pez06:05:17

I think this will be fixed with next release of clojure-lsp: https://github.com/clojure-lsp/clojure-lsp/issues/982

maxt06:05:03

Ah, wow, that was a solution on a different level than I'd expected. The most important part for me is that new users don't get tripped up, but it seems that you're on it then, great!

zakkor06:05:41

I stumbled upon this annoyance too

pez15:05:32

If you stop and start clojure-lsp this will be fixed. I just tested it. 🎉

maxt06:05:51

Yep, it works! Thanks

pez15:05:48

Music to my ears! Please head over to #announcements and throw your reactions of appreciation on this one, dear Calva and clojure-lsp friends! UPDATE: To install, stop, and then start clojure-lsp again. (Both available from the clojure-lsp status bar item.)

🚀 5

💜 3

mathpunk16:05:03

I always used ,. to get into Paredit mode in Emacs and I'd like to change the keybinding from ,k in VSSpaceCode. I tried to edit the configuration file but it's in read-only mode :thinking_face:

mathpunk16:05:06

I found it as defaultSettings.json. So far I haven't found a way to exit read-only mode

pez16:05:03

No idea, tbh. I'd google ”VSSpaceCode config readonly” or something.

pez16:05:35

As for the toggle. There's very little reason to toggle Paredit off. It only affects how backspace and delete function, which is even less relevant with VIM-ish bindings.

mathpunk16:05:00

agreed

2022-05-23

Channels