I'm having an issue I've posted about in #cider that's stumping me. I use Emacs in a terminal and also CIDER. C-c C-d C-d opens up cider-doc for the symbol under the point without issue in a split. However, C-c C-d C-c, bound to cider-clojuredocs, prompts for the symbol under the pointer (doesn't pick it up like cider-docs) then hangs there. At one point C-h f indicated it was looking in a path that was for an older version of CIDER than I have installed, but that path vanished from the binding description. Any tips on how to get cider-clojuredocs to open in a split like cider-docs does? edit: C-c C-d C-w opens clojuredocs in the browser, if that's a helpful clue.
Do you have the latest CIDER version?
I see you replied in the other thread. I would suggest completely removing CIDER and then installing it from ELPA again.
You can delete all cider directories from .emacs.d/elpa to be sure
I'll remove it all. I did it once in this process, but maybe another go will help. I do have the latest CIDER version. In the other thread it momentarily seemed like I don't, but what was really going on is that, apparently, cider-clojurescript was looking in a path that reflected an older version. I'll update here once I reinstall everything.
Hmm... reinstalled, running
CIDER 1.17.1 (Cologne)
and still having the issue. C-c C-d C-d (cider-docs) works, C-c C-d C-w (clojuredocs on web) works, but C-c C-d C-c (cider-clojurescript) hangs.
__________________________________
I created a minimal .init.el with just cider and ran emacs in terminal (as opposed to iTerm 2) and am still had the issue. I'm using the lates Emacs and CIDER.
__________________________________
I then installed a separate GUI emacs and created a fresh minimal init file (just cider). Same problem. Also, same problem on my old machine which cider-clojuredocs worked on, and in which there have been no changes.
It seems like this actually might be a CIDER issue at this point, but I'll have to step away and reassess with a fresh mind in a bit.
Also, apologies for starting the thread and picking it up here in #emacs I assumed it was an Emacs issue at a certain point (and it likely is, but most probably a PEBKAP one).