Fork me on GitHub
#cider
<
2021-08-09
>
djm05:08:11

The closest thing I know of is lsp-ui-peek-find-definitions (Although it’s a popup rather than the echo area).

👀 5
vemv06:08:39

does it work with clojure-lsp?

djm06:08:14

Yes

👍 5
djm07:08:36

But don’t let that stop you from contributing your version - I’d love to have that in CIDER

vemv07:08:30

:) yeah not at all, it simply piqued my curiosity

bozhidar09:08:37

Yeah, there's nothing like this in CIDER, so feel free to contribute it. I recall some people asked for something similar in an overlay, which also makes sense to me.

cider 2
drewverlee16:08:42

Is there a way to have the emacs client install the matching version on its side on a per project basis? I understand typically you think to sync the other way to avoid these errors:

WARNING: CIDER 1.2.0-snapshot requires cider-nrepl 0.26.0, but you're currently using cider-nrepl 0.22.0-beta4. The version mismatch might break some functionality! (More information)
WARNING: clj-refactor and refactor-nrepl are out of sync.
Their versions are 2.5.1 (package: 20210628.1154) and 2.5.0-SNAPSHOT, respectively.
You can mute this warning by changing cljr-suppress-middleware-warnings.
But sometimes it feels safer to use the same setup as the project/author.

vemv17:08:02

It would be pretty rare for a project to depend on a specific CIDER feature... normally I place cider-nrepl in my ~/.lein/profiles.clj so that it will take precedence

vemv17:08:01

trying to answer to your q, a hardcore way would be to remove cider as an elpa dep, and use a git submodule instead. And one would switch tags as one switches projects

bozhidar20:08:36

To me it seems easier to just have some shared profile with the nREPL deps for all your projects. I assume those warnings are coming because some deps are added to each project or something along those lines, as with jack-in CIDER would have just added the optimal versions.

4