'Wrong type argument: arrayp, nil' on cider-jack-in

[noisegul]

Expected behavior

Starting a REPL with cider-jack-in

Actual behavior & Steps to reproduce the problem

When trying to use cider-jack-in while editing a single *.clj file that is not part of a project, this error occurs. Starting a nREPL server separately and connecting to it works as expected. Starting a REPL with cider-jack-in inside a project created with boot-new works fine as well.

Environment & Version information

CIDER version information

;; CIDER 0.14.0snapshot (package: 20160727.904), nREPL 0.2.12
;; Clojure 1.8.0, Java 1.8.0_92

Boot version

BOOT_VERSION=2.6.0

Emacs version

GNU Emacs 25.0.94.2

Operating system

Windows 10

[Malabarba]

You're not the first to run into this. It seems to be a regression in Emacs 25. I guess someone needs to report it. :-)

[bbatsov]

//cc @NicolasPetton

[NicolasPetton]

@bbatsov do you know where the bug comes from? A stacktrace would be perfect.

[bbatsov]

@bitrauser can you post here the backtrace as well?

[hackeryarn]

I am having the same issue but while working in a cljs project and a different emacs version. Happens with both cider-jack-in and cider-jack-in-clojurescript.

Debug trace

Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
  replace-regexp-in-string("[^-0-9a-zA-Z_./\n]" "\\\\\\&" nil)
  shell-quote-argument(nil)
  cider--lein-resolve-command()
  cider-jack-in-resolve-command("lein")
  cider-jack-in(nil)
  call-interactively(cider-jack-in record nil)
  command-execute(cider-jack-in record)
  #[257 "\304\305!\203\f�\306\307�!!\210��\307�!\211��\310\307�!\311\")\207" [current-prefix-arg prefix-arg this-command real-this-command featurep smex smex-rank intern command-execute record] 4 "\n\n(fn CMD)"]("cider-jack-in")
  ivy-call()
  ivy-read("M-x " [emmet-filters esh-arg dired-view-file bibtex-autofill-entry viper-util x-sensitive-text-pointer-shape ox-man debugger-previous-window verilog-mode-indent org-export-org dired-faces web-mode-unfontify-region erc-log web-mode-interpolate-javascript-string misearch web-mode-file-extensions nnir web-mode-django-code-font-lock-keywords web-mode-element-wrap ediff-merg nnmail-files gnus-article-highlight cal-html ezimage-document-minus web-mode-block-is-opening-control erc-mode-line-and-header icomplete concat-str dired-find-subdir gnus-score-expire kill-grep epl-package--parse-info elt-clo erc-autoaway srecode/expandproto web-mode-tag-next-position custom-faces em-script web-mode-part-highlight tag-flags widget-radio-value-get doc-view-get-bounding-box ebrowse xscheme none-but-delete message-buffers speedbar-directory-face ps-print-printer ob-R alchemist-compile--file ...] :predicate commandp :require-match t :history extended-command-history :action #[257 "\304\305!\203\f�\306\307�!!\210��\307�!\211��\310\307�!\311\")\207" [current-prefix-arg prefix-arg this-command real-this-command featurep smex smex-rank intern command-execute record] 4 "\n\n(fn CMD)"] :sort t :keymap (keymap (67108908 . counsel--info-lookup-symbol) (67108910 . counsel-find-symbol)) :initial-input "^" :caller counsel-M-x)
  counsel-M-x()
  call-interactively(counsel-M-x nil nil)
  command-execute(counsel-M-x)

Emacs version

GNU Emacs 24.5.1 (x86_64-apple-darwin15.0.0, NS apple-appkit-1404.13

[NicolasPetton]

That's Emacs 25.4, so I guess the bug is in CIDER, not in Emacs 25.1 RC? shell-quote-argument is called with nil.

[hackeryarn]

To help with reproduction. I got the error initially while working on a reagent project. So I tried to generate a fresh reagent project which resulted in the same thing. Seems that thereagent and re-frame lein templates lead to this error. I also tried both with +cider and without and got the same results.

[bbatsov]

Hmm, seems lein is not on exec-path in those scenarios. Guess I didn't consider this.

[hackeryarn]

@bbatsov would it need to be added to emacs exec-path manually? Because it's definitely in my system path.

[bbatsov]

Usually - yes. You can also use https://github.com/purcell/exec-path-from-shell

[Malabarba]

@achernyak You need that the environment that Emacs is started in be the same as the environment where you set up your path. How to actully do that varies between system. exec-path-from-shell is one option.