cider

macrobartfast 2025-04-01T02:43:35.723589Z

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?

oyakushev 2025-04-01T15:06:09.403829Z

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.

macrobartfast 2025-04-02T00:38:19.140009Z

That's helpful info. It means it's my setup and not that ClojureDocs is down. I'll try a new project.

macrobartfast 2025-04-02T00:42:12.334659Z

The problem exists is different projects. cider-doc works but not cider-clojuredocs.

macrobartfast 2025-04-02T00:43:18.542309Z

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]

macrobartfast 2025-04-02T00:43:47.217219Z

The 'Cannot open doc string file...'

macrobartfast 2025-04-02T00:59:22.538179Z

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).

macrobartfast 2025-04-02T02:18:45.288089Z

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.

bozhidar 2025-04-02T07:28:33.637789Z

@macrobartfast There's nothing in the clojuredocs commands that shouldn't work in a terminal. The UI there is pretty basic.

bozhidar 2025-04-02T07:29:16.326019Z

I see you're using a pretty old version of CIDER, so you might want to update it.

bozhidar 2025-04-02T07:29:27.539879Z

(it's like 10 releases old)

macrobartfast 2025-04-06T05:42:18.744229Z

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.

bozhidar 2025-04-06T14:56:33.513479Z

Might be a good idea delete the byte compiled files or even reinstall CIDER.

macrobartfast 2025-04-07T00:54:46.476599Z

I've reinstalled CIDER; does that also delete the byte compiled files?

bozhidar 2025-04-07T06:31:34.810479Z

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.

👍 1
oyakushev 2025-04-01T15:10:42.931509Z

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.

7
❤️ 11
😍 3