Fork me on GitHub
#calva
<
2022-10-03
>
skylize16:10:08

I just accidently pressed some unknown button combination and it prefixed a symbol with a colon. Is this a Calva command?

pez16:10:52

Not a command that I know of. 😃

pez16:10:31

Did it not move the cursor to the start of the symbol, you mean?

skylize18:10:48

Cursor was at right end after the symbol, and stayed at right end when a colon appeared in front of symbol and highlighting changed to indicate keyword. Ctrl-Z removed the colon, still without moving the cursor.

seancorfield23:10:15

Calva seems to auto-insert :require clauses for namespaces I reference in comment forms. I remember it asking me about a refactoring a while back and I said "yes, always do this" but now I can't find that setting to turn it back off (what I really wanted was "no, and don't ask me again" I suppose). Where do I find/reset such settings?

pez05:10:32

I’m not aware of such a setting. Could it be a clojure-lsp thing?

seancorfield09:10:34

I wonder if it is stored in the local DB file? Maybe the only way to reset it is to blow away that file...

Max18:10:55

I ran into this a while back. If it’s one of those vscode-native popups confirming that you want to take an action offered by the LSP, e.g. “you moved this file, would you like to update all the references to it”, then the only way to reset it is to either blow away VSCode’s local state or figure out how to alter the setting in that state. I spent a bunch of time figuring out how to do option 2 a while back but I don’t remember all of the details. I think I posted about it some in this channel? Here’s a vscode ticket requesting a less awful way to reset these: https://github.com/microsoft/vscode/issues/24815

seancorfield20:10:46

@U01EB0V3H39 Thanks! Good to know that this is VS Code, not Calva/LSP, but also terrible to hear they're just JSON blobs in a SQLite DB with no other way to modify them 😞

💯 1