Fork me on GitHub

does anyone else use inf-clojure with boot? I think it's completely busted. Running inf-clojure with lein repl works just fine, but starting an inf-clojure with boot throws an eldoc error each time you try to type something


here's the stacktrace:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("\\Ca*true\\Ca*" nil nil)
  #[257 "\301\302\303\304#)\207" [inhibit-changing-match-data "\\Ca*true\\Ca*" nil t string-match] 8 "\n\n(fn STRING)"](nil)
  inf-clojure--response-match-p("(js/global.hasOwnProperty \"$$LUMO_GLOBALS\")" #[257 "\301\302\303\304#)\207" [inhibit-changing-match-data "\\Ca*true\\Ca*" nil t string-match] 8 "\n\n(fn STRING)"] #<process inf-clojure<1>>)
  apply(inf-clojure--response-match-p ("(js/global.hasOwnProperty \"$$LUMO_GLOBALS\")" #[257 "\301\302\303\304#)\207" [inhibit-changing-match-data "\\Ca*true\\Ca*" nil t string-match] 8 "\n\n(fn STRING)"] #<process inf-clojure<1>>))
  inf-clojure--lumo-p(#<process inf-clojure<1>>)
  inf-clojure--detect-repl-type(#<process inf-clojure<1>>)
  inf-clojure--set-repl-type(#<process inf-clojure<1>>)
  inf-clojure-eldoc-arglists(#("nREPL" 0 5 (fontified t face clojure-interop-method-face front-sticky (field inhibit-line-move-field-capture) rear-nonsticky t field output inhibit-line-move-field-capture t)))
  #[0 "\204	\205\n\303>?\205\304 \207" [eldoc-mode global-eldoc-mode eldoc-documentation-function (nil ignore) eldoc-print-current-symbol-info] 2]()
  apply(#[0 "\204	\205\n\303>?\205\304 \207" [eldoc-mode global-eldoc-mode eldoc-documentation-function (nil ignore) eldoc-print-current-symbol-info] 2] nil)
  timer-event-handler([t 0 0 500000 nil #[0 "\204	\205\n\303>?\205\304 \207" [eldoc-mode global-eldoc-mode eldoc-documentation-function (nil ignore) eldoc-print-current-symbol-info] 2] nil idle 0])


it's got a bunch of stuff about Lumo in there, when I'm running a boot repl, so I'm pretty confused. @richiardiandrea @bozhidar


I don’t have any time to debug this. I find it pretty odd overall that the REPL started by boot would behave differently, though.


Agree that it is odd, but there is some code that executes initially that tries to detect which repl type we are on, I will try to debug it asap, can you please report it as issue @adamfrey?