I suspect this is more of a general VS Code Q: as of maybe today, tab in the terminal no longer autocompletes against filenames but instead tabs to another part of the UI. Any suggestions for debugging/fixing this?
Weird... it was only in one project and when I restarted VS Code in that project, it was fine. π€·π»ββοΈ
Dear Calva friends: calva https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.585 β’ Fix: https://github.com/BetterThanTomorrow/calva/issues/3211
OMG! Thank you for this fix! It's been driving me nuts and I've mentioned it in #lsp several times -- sometimes the build system breaks, I think? -- so it's really nice to see a fix in Calva directly, so I don't have to switch back and forth between latest and nightly π
Haha, thatβs how I have solved it too. I hope this will fix it. The main strategy is to keep using the existing binary and the upgraded one will be used on next start of clojure-lsp. (Which could be a manual restart or reload of the VS Code window.) And then there are some more things that I think improves things as well, especially in the start-of-vscode scenario where potentially several Calva instances start at once.
Hi all! Cursive allows for highlighting clojure.core functions with their own color. Can this be done in Calva?
Thereβs no current feature like that. May be something for clojure-lsp, @ericdallo?
currently clojure-lsp doesn't do that and I wonder if that should be really done, but it's totally possible, can you show some screenshots? also only clojure.core? what about clojure.string or other ns? and clojurescript? so many questions
just core
I wouldn't go as far as arguing it should be done π. But I like it and have grown accustomed to it
I don't mind rolling my own if I have to. Just wanted to make sure I have to
that's a interesting thing, I can see arguments from both sides, like "in the end everything is a function or macro so no reason to color differently", but maybe we could offer this a option, feel free to create a issue in clojure-lsp
tbh I like the macros/specials getting the different highlighter better, perhaps you should see if it grows on you if you're switching
yeah, maybe. But I have been looking at it for 10+ years now. Hopefully it'll take less than that
I'd be ok with options in clojure-lsp settings to say whether to enable this kind of feature, there is no final answer I think, only personal preference
Thanks!
@ericdallo bb cli-prod-jar will get me the jar the path of which I need to set in Calva's Calva: Clojure Lsp Path setting, right?
Sweeet!
Or you can bb debug-cli which will give a binary to just point to it from calva :)
doesn't have one π
well, now it's called firefly
enjoy
you'll need this PR on clojure-lsp https://github.com/clojure-lsp/clojure-lsp/pull/2288
otherwise the core functions will have the same color than other functions
I don't remember how it came to be tbh. Just me customizing some Intellij theme many years ago
I think I was still working with Python at the time
which is ironic because after a decade I am back to it, sadly. Which is why I need Calva now, to get those dialects working
Not letting those parens go quietly into the night π
Awesome, thanks
@hjrnunes What is the name of your VSCode theme? :) I like it!