Peter Strömberg
Peter Strömberg
You probably have semantic tokens disabled.
We should fix both. It's probably pretty easy.
Hello. What output do you have in the **Terminal**? (If there are several terminals started, the one labeled **Calva Jack-in** is the relevant one.
@bpringe That warning could be related, but the problem here is that the REPL isn't connected. The output/repl window, which does not show the repl start and connection process and...
Hello. It is a bit of a mystery to me how Leiningen treats: * command line provided configuration * configuration provided in the user profile * configuration provided in the...
npm audit doesn't bring this up. Just noting this as one of the clues.
The warning comes from a use of yauzl. ``` ~(:|✔) % export NODE_OPTIONS=--throw-deprecation ~(:|✔) % code-exploration --install-extension betterthantomorrow.calva Found 'betterthantomorrow.calva' in the marketplace. Installing... internal/process/warning.js:143 throw warning; ^ DeprecationWarning: Buffer()...
This warning used to come from VS Code itself using yauzl. They fixed that some year ago, if I understand the issues correctly.
I have missed this suggestion. It makes sense.
There is currently no way to get rid of that step. We should maybe fix that. Iirc, the autoConnect setting is about when Calva starts, if it should automatically connect...