Clojurians Log v2

There is a concept of project type used for launching the nRepl server and then cljs repl type for automatically execute the cljs upgrade cimmand in the Clojure repl. Both prompt in case of inconsistent detection and they they don't prompt in case of defaults

@rymndhng What I meant was that the detection mechanism gets brittle as the number of possibilities explode. The actual injection of dependencies stabilizes things, as you point out. Another reason to mimic Cider here (apart from that Calva's name demands it :face_with_cowboy_hat:) is to be able to shrink the Getting Started text to a minimum. There is something wrong when I have to spend so much of it on talking about dependencies (failing in most cases to help people anyway).

I miss this kind of feature in Emacs https://github.com/magit/magit/issues/2942 - clojure-specific syntax highlighting in diffs, so I can code-review stuff more accurately.

I know IntelliJ does this pretty well, how about vim? Apparently it also features this. I guess one could use vim as an improved git show / git diff?

If anyone has this setup already (or can, easily) I'd appreciate some guidance 🙂

Vim doesn't do any better when looking at a diff.

Gitgutter is useful some of the time, but isn't generalized to diffs.

Useful, thanks. Recently I tried to hack <https://github.com/syohex/emacs-git-gutter/> to generalize it to diffs, but wasn't trivial

VS Code handles this nicely, using the regular edit buffers for diffing and overlaying the syntax colored text with transparent diffing colors.

Which means Calva can still help you evaluate Clojure code and such even when diffing. I have had use for that a few times.

re command not found: I also had this yesterday and ended up reinstalling Calva since it seemed like it wasn't properly installed or activated. Regardless of whether that was the correct assessment it worked after reinstalling 😄 /cc @kmiasko

https://code.visualstudio.com/assets/docs/editor/versioncontrol/merge-conflict.png this is lovely

@martinklepsch: There is a an irritating error where Calva refuses to activate when the first file opened is not a clojure file. Not sure if that was what happened in your case, but anyway, I must spend some time to try pin it down. VS Code loves to open up all sorts of files at startup, unprompted by the user.

it could be but I'm not sure... could Calva delay activation until a clojure file is opened?

would that make sense?

That is what it tries to do today. Maybe I should look for a way to always activate it instead. I hesitate because I suspect the issue is just a symptom for something I should fix and not hide. 😃

I probably shouldn't admit this, but Calva still has a command that activates it. Problem is that Calva can't register the command without being activated. 😲 Late night hacking is not always the best idea.