Closed pvik closed 5 years ago
I had a quick investigation of this and seem to have it working by changing one of the functions in flycheck-clojure.el
(defun flycheck-clojure-may-use-cider-checker ()
"Determine whether a cider checker may be used.
Checks for `cider-mode', and a current nREPL connection.
Standard predicate for cider checkers."
(let ((connection-buffer (cider-current-repl)))
(and (bound-and-true-p cider-mode)
connection-buffer
(buffer-live-p (get-buffer connection-buffer))
(clojure-find-ns))))
Seems like cider's session management was updated and a lot of the API was trimmed (you can see the commit here). You can pull the repl buffer using the new cider-current-repl
function rather than (cider-default-connection :no-error)
which was being used previously.
I'm not involved in this project so maybe one of the maintainers wants to turn this into a PR (I'm not sure if theres other bugs introduced from the cider API refactor), but you can at least do this for a temporary fix.
Thanks for looking into this. I've merged your change, and it should make to melpa in a day or two.
Has this been resolved? I'm facing the same issue.
cider-default-connection
has not been used since 353e6aa0b807f0126d145ac69443db1ee2b6b57c, last July. You must be using an old version.
Since cider has moved to sesman to handle connections to the repl, when using squiggly-clojure I am getting the following error:
While compiling squiggly-clojure I have these messages in my
*Compile-Log*