cider 2020-05-07 | Slack Archive

Both the content-type bugfixes and the new default are only the snapshot.

🎉 4

i see two candidates for cider-nrepl. which is supposed to be used right now?

0.25.0-SNAPSHOT
0.25.0-alpha1

bozhidar04:05:02

Both will work - in CIDER the required version is alpha1, but I updated the snapshot as well, because I noticed many people using cider-connect still believe they have to use the same cider-nrepl version as CIDER’s version.

dpsutton16:05:23

i'm getting lots of errors from the middleware and just want to make sure i'm using the most recent. also is nrepl 0.7 a hard dependency or optional?

bozhidar04:05:02

What kind of errors? nREPL 0.7 is not a hard dependency - I bumped it mostly to verify it’s working well for everyone.

Parenoid21:05:39

M-x cider-clojuredocs in terminal emacs is throwing

Wrong type argument: char-or-string-p, nil

with the following debug statement

Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
  cider-clojuredocs--content(nil)
  cider-clojuredocs-lookup("get")
  cider-read-symbol-name("ClojureDocs doc for" cider-clojuredocs-lookup)
  cider-clojuredocs(nil)
  funcall-interactively(cider-clojuredocs nil)
  #<subr call-interactively>(cider-clojuredocs record nil)
  apply(#<subr call-interactively> cider-clojuredocs (record nil))
  call-interactively@ido-cr+-record-current-command(#<subr call-interactively> cider-clojuredocs record nil)
  apply(call-interactively@ido-cr+-record-current-command #<subr call-interactively> (cider-clojuredocs record nil))
  call-interactively(cider-clojuredocs record nil)
  command-execute(cider-clojuredocs record)
  execute-extended-command(nil "cider-clojuredocs")
  (with-no-warnings (execute-extended-command current-prefix-arg chosen-item-name))
  (unwind-protect (with-no-warnings (execute-extended-command current-prefix-arg chosen-item-name)) (smex-rank chosen-item))
  (if smex-custom-action (let ((action smex-custom-action)) (setq smex-custom-action nil) (funcall action chosen-item)) (unwind-protect (with-no-warni$
  (let* ((chosen-item-name (smex-completing-read commands initial-input)) (chosen-item (intern chosen-item-name))) (if smex-custom-action (let ((actio$
  smex-read-and-run(("list-buffers" "cider-clojuredocs" "cider-scratch" "toggle-debug-on-error" "cider-connect" "linum-mode" "cider-version" "indent-r$
  (if (smex-already-running) (smex-update-and-rerun) (and smex-auto-update (smex-detect-new-commands) (smex-update)) (smex-read-and-run smex-ido-cache$
  smex()
  funcall-interactively(smex)
  #<subr call-interactively>(smex nil nil)
  apply(#<subr call-interactively> smex (nil nil))
  call-interactively@ido-cr+-record-current-command(#<subr call-interactively> smex nil nil)
  apply(call-interactively@ido-cr+-record-current-command #<subr call-interactively> (smex nil nil))
  call-interactively(smex nil nil)
  command-execute(smex)

any thoughts on how to figure this out?

Parenoid21:05:59

using CIDER 0.24.0 (India)

Parenoid22:05:34

I've been staring at https://github.com/clojure-emacs/cider/blob/master/cider-clojuredocs.el but it's a bit hard for me to figure out.

Parenoid22:05:28

since I'm in emacs -nw terminal, I wonder if pop-to-buffer in cider-clojuredocs--content, the last call in the stack.

Parenoid22:05:10

the problem seems to be in

(let ((docs (cider-sync-request:clojuredocs-lookup (cider-current-ns) sym)))

and that is pretty hard for me to figure out.

yuhan01:05:02

Is your cider-nrepl version in sync? Try evaluating (cider-nrepl-op-supported-p "clojuredocs-lookup")

bozhidar05:05:32

My guess would be that something’s wrong with the local copy of the clojuredocs database or something along those lines. Still, it seems we should have also added a nil check for missing content.

Parenoid05:05:24

aha ok I didn't realize it was going to a local copy of the clojure database...

Parenoid05:05:39

wondering where/how should I evaluate

(cider-nrepl-op-supported-p "clojuredocs-lookup")

I was just reading the code in the github repo and that's where I studied the line of code the debugger revealed... evaluating your suggestion in cider-scratch gives me an

Unable to resolve symbol: cider-nrepl-op-supported-p in this
   context

Parenoid05:05:51

probably because that's not I should do that.

Parenoid05:05:18

@U051BLM8F is there a way for me to troubleshoot the possibility off an issue with my local database (or maybe just reinstall or whatever)?

Parenoid05:05:44

@UCPS050BV I also tried

(cider-nrepl-op-supported-p "clojuredocs-lookup")

in the minibuffer and it returned nil... not sure if there was an error as I don't know where to look.

Parenoid05:05:40

I did that with M-x eval-expression.

yuhan05:05:10

It might be a cider-nrepl mismatch in that case - check the first few lines of your cider-repl buffer which should state the version

Parenoid05:05:34

REPL-y 0.4.3, nREPL 0.6.0
Clojure 1.10.0

Parenoid05:05:49

are they supposed to be the same version number... or?

bozhidar05:05:05

We need info from CIDER’s REPL buffer. I think what you shared is from lein repl.

bozhidar05:05:57

> are they supposed to be the same version number... or? Not necessarily - in CIDER there’s a variable cider-required-middleware-version that specifies the required cider-nrepl version.

Parenoid05:05:42

I'm so dense... where do I evaluate that?

Parenoid05:05:00

getting unable to resolve symbol.

Parenoid05:05:24

or is it something in configuration?

Parenoid06:05:43

oh... doh. I finally just understood what you meant @U051BLM8F about looking at CIDER's REPL buffer.

Parenoid06:05:14

YAAAAAY! I have clojuredocs. Thank you all so much for the help, and thanks for the patience.

bozhidar12:05:36

So, what was causing the problem for you?

2020-05-07

Channels