Clojurians Log v2

@pez creating a cljs repl failed for him:

Calva activated. Happy Clojure(script) coding! ❤
Please file any feature requests or bug reports here: <https://github.com/PEZ/clojure4vscode/issues>
I will also respond to any @pez mentions in the #editors channel of the Clojurians Slack: <https://clojurians.slack.com/messages/editors/>

NOTE: Files are no longer automatically evaluated when opened. You will need to issue the evaluate file command at will instead.
NOTE: The evaluate file command does not seem to work in shadow-cljs clojurescript repls. A workaround, that someetimes suffices, is to select all contents of the file and evaluate it.

NOTE: All Calva settings have changed prefix from 'clojure4vscode' to 'calva'. (I am sorry for the inconevience.)

NOTE: Autolinting is disabled. You need to enable "calva.lintOnSave" in your editor settings to use it. But first install Joker: <https://github.com/candid82/joker>
Autoconnecting... (This can be disabled in Settings)
This looks like a shadow-cljs coding session.
Hooking up nREPL sessions...
Connected session: clj
Terminal created for: Clojure REPL
Failed starting cljs repl for shadow-cljs build: :browser
cljc files will use the clj REPL.
This looks like a shadow-cljs coding session.
Disconnected session: clj
Hooking up nREPL sessions...
Connected session: clj
Terminal created for: Clojure REPL
Failed starting cljs repl for shadow-cljs build: :browser
cljc files will use the clj REPL.

Finally we got the time to do a proper editor setup.

@mynomoto Is the app connected and running in the browser?

Oh, that makes sense. Trying it now.

It worked!

Wonderful. I should probably add that to the error message,

Is there a way to connect to the cljs repl without reopening the project? I have no idea of how vscode works and my colleague is not familiar with plugins.

Alll calva commands can be seen if he does cmd+shift p and searches for calva.

I was following the instructions on the plugin page so you could add it there too.

There is a “Connect command”. ctrl+alt+v c, I think that is what you need.

cmd+shift p is going to be very useful. Thanks!

Yes, it is the power command shortcut in VSCode. 😃

How one triggers autcomplete?

cmd+p as well.

Evaluate the file. Currently the evaluate file command fails in shadow-cljs projects. But selecting all and evaluate selection ctrl+alt+v e most often does the trick.

Autocomplete should just happen. At least if the file is evaluated. Maybe ctrl+space can trigger it at will.

So it works but it's inconsistent. He typed (str/ and it showed completions. Then he deleted the / and typed it again, it didn't show. Doing it again showed completions. And it keeps alternating showing completions and not showing them.

Ah, that’s strange. Let me try…

Yes, there seems to be something strange around the fourth character. Don’t know if it is Calva or Code that is acting up. I’ll have a check. Thanks for the heads up!

When I try it now at least I get a more consistent behaviour when adding a few chars more.