newest cider requires paredit-24, but emacs comes bundled with paredit-22. can anyone point me to a snippet that'll force the correct version of paredit to be installed from melpa, please?
root cause: i had the wrong melpa domain in my package list :face_palm: .
I'm working on files mounted via a network share while connected to a REPL on the remote machine
I was hoping that cider-find-var
would work, since the paths stored as metadata on the vars are relative
I guess I'll have to write some elisp myself unless someone has an idea here
Maybe cider could support some base-path setting which accounts for the difference in mount point
I've made a horrible horrible hack and made a directory in linux named /Users/borkdude/mnt/dre/DocSearch/app
so I have exactly the same paths on linux and macOS
And now it works 😂
Borkdude check out “cider-path-translations”
I use it for docker but it might work here
wow... interesting... !
We got some elisp, if that does not work
https://github.com/akvo/akvo-lumen/blob/master/backend/.dir-locals.el
@kardan that was my exact motivation. It might work for you
(as in if it’s not available in the version). Using the cider-path-translation sound like the goto path
🙂
How do I clear settings that were in dir-locals? I got it wrong the first time and now it seems they are cached somewhere?
never mind, restarting worked. this is AWESOME!
With a lot of disclaimers I think you can close buffers that lives in that path and then reopen
Does CIDER make use of javadoc-only dependencies in the form of [<http://some.third.party/dep|some.third.party/dep> "1.10.1" :classifier "javadocs"]
?
My impression (from skimming the .el code) is that not. Which wouldn't be much surprising, as parsing javadocs' .html sounds like a pain :)
It does.
Just isn't anything to do with .el. It's in orchard.
Issue with CIDER 0.26 and 0.27.0snapshot and babashka + cider-doc
:
https://github.com/babashka/babashka.nrepl/issues/26
I've cut 0.26.1 that includes the fix for this bug.
:thumbsup:
I wanna add a custom cider-debugger command. Has anyone done something like that?
I think you can just check the code for the existing commands. It's relatively straightforward.