cider-clojuredocs seems to hang in the minibuffer. Well... I have it mapped to a binding, but it no longer picks up the symbol under the point, and asks 'ClojureDocs doc for?' in the minibuffer, then hangs after I've supplied it. any tips?
Does it happen in every project? I've just tried, and Clojuredocs seems to work for me. I put the cursor over a function in a code buffer, do M-x cider-clojuredocs and it works.
That's helpful info. It means it's my setup and not that ClojureDocs is down. I'll try a new project.
The problem exists is different projects. cider-doc works but not cider-clojuredocs.
Possible clue from revealing what my binding refers to
C-c C-d C-c runs the command cider-clojuredocs, which is an
interactive byte-compiled Lisp function.
It is bound to C-c C-d C-c, C-c C-d c and <key-chord> " ".
(cider-clojuredocs &optional ARG1)
Cannot open doc string file "/Users/glow/.emacs.d/elpa/cider-1.7.0/cider-clojuredocs.elc"
[back]
The 'Cannot open doc string file...'
I did just discover C-c C-d C-w which opens the clojuredocs in a tab successfully, which is a good thing for now (and possible another clue).
I use terminal emacs, so I'm beginning to wonder if the problem is that cider-clojuredocs is trying to open a popup (which isn't supported in a terminal) rather than a new buffer. And so the apparent 'hang' is really the fact that a popup isn't opening.
@macrobartfast There's nothing in the clojuredocs commands that shouldn't work in a terminal. The UI there is pretty basic.
I see you're using a pretty old version of CIDER, so you might want to update it.
(it's like 10 releases old)
Thank you for this! Actually, I'm using the current CIDER version, so what's going on is that the command is looking for an older version. In other words, that path isn't accurate to my current version. The error message reveals this. However, weirdly, C-h K isn't showing this error message now, but it still hangs. Another computer I have with the same setup is also now hanging in the minibuffer when it worked before. The mystery continued, but I'll chip at it.
Might be a good idea delete the byte compiled files or even reinstall CIDER.
I've reinstalled CIDER; does that also delete the byte compiled files?
I think it does. You might also want to remove whatever old installations of CIDER you have lying around. I think package.el had some commands to remove obsolete packages.
cider CIDER news cider: The latest rolling version enables more flexible code completions by default. This a reminder for you that CIDER can complete things like these (see screenshots). All supported completion scenarios for Compliment (and thus CIDER) are listed https://github.com/alexander-yakushev/compliment/wiki/Examples.