Clojurians Log v2
calva
@ryan072 Sounds very professional. Alas I do not have that level of experience to realize your technique. In fact, I still struggle with the whole REPL approach, which isn't a productive tool to me yet. (Often times it simply doesn't work/connect.) I dearly miss debugging (debugger) in Clojureworld. Sad to say after 2 years of Clojure I still depend on:
let [... log (str "my-var-to-check: " my-var-to-check ...]
Pathetic. But the barriers to Clojureworld (to me) are not the language. It's the ecosystem. In fact, I have no problems traversing tree structures via stack algorithm and loop/recur. No problem to my brain. But the whole tooling in Clojure is still a mystery to me.
That was my experience too. And then at some point, something changed and everything became easier. I do think calva getting more stable was a part of that. So best of luck!
Also Sean corfield is giving a talk today on repl driven development. So that may be worth watching (I’ll be watching)
I hope you don’t mind: https://calva.io ❤️
@ryan072 Excellent! where could I catch that? (as a side note, the Clojure community is just aweseome!)
it's in an hour. and sean said the vod will be posted somewhere
I'd prefer not to have that on the page if you don't mind :)
ah. I just signed up to meetup, then was given the link. Alas I don't do zoom. (Simply no camera nor microphone on my linux laptop here.) If there will be a VOD afterwards I better take that option. (Otherwise I pose an irritation to the rest of you guys. A thousand thanks for the link+opportunity!)
Oh noes! But I’ll remove it then, of course.
Done!
thx
With VSpaceCode, I am excited to be giving Calva another whirl! (my poor old brain is very used to spacemacs key bindings).
3🎉
Calva version 2.0.149 is out with the following fixes: • Fix: https://github.com/BetterThanTomorrow/calva/issues/933`${env:...}` • Update clojure-lsp to version 2021.01.12-02.18.26. Fix: https://github.com/BetterThanTomorrow/calva/issues/906
@borkdude In my testing of the above, I noticed the clj-kondo server was also orphaned / left running sometimes. It may be an even smaller chance with the kondo server, but see the fix here if you want to implement this fail-safe exit. https://github.com/clojure-lsp/clojure-lsp/pull/251/files
You can see more info about this https://github.com/microsoft/vscode-languageserver-node/issues/726#issuecomment-757687189, where it was explained that aside from a bug in vs code, servers should use the processId in the initialize request to check if the parent process is alive, and exit if it's not.
@brandon.ringe Thanks a lot! Made an issue here: https://github.com/clj-kondo/clj-kondo.lsp/issues/14
1👍2