This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (29)
- # boot (17)
- # calva (1)
- # cider (31)
- # cljs-dev (3)
- # clojure (169)
- # clojure-europe (1)
- # clojure-france (1)
- # clojure-russia (40)
- # clojure-serbia (3)
- # clojure-uk (42)
- # clojurescript (19)
- # clr (3)
- # core-async (7)
- # core-typed (3)
- # cursive (43)
- # datascript (4)
- # datomic (2)
- # dirac (4)
- # emacs (2)
- # fulcro (85)
- # funcool (1)
- # nrepl (5)
- # off-topic (14)
- # shadow-cljs (28)
- # spacemacs (5)
- # tools-deps (2)
I heard a rumor about a breaking change in error messages causing 1.10 not to work well with Cider
@m131 ac-cider was deprecated a while ago and I’m not even sure it’s working these days. We encourage everyone to use company-mode together with CIDER (or some other completion engine using the standard completion-at-point functionality of Emacs).
I haven’t had time to test 1.10 yet, so I’m not certain about the extent of the breakage or whether the fix that was merged to fix this actually fixed the problem.
Yes, the instructions on http://clojure.org apply to 1.10 now and I wanted to try out the deps.edn technique, specifically because it promises we may depend directly on a Git tag, not via Clojars. Indeed, an announcement already appeared on the Clojure Google Group saying "We'll no longer be publishing ... to Clojars". That library was a special case, but I expect it will be the way forward - more flexible and less hackable surface area.
The problem occurred when rendering a stack trace. So just don't have any errors in your code 😊
I am using cider-find-var to jump to various definitions to see what they are; I then want to jump back to the invocation; is there a binding or function that will do that? I've searched and the various answers I saw require me to set a mark or register before jumping to the definition, but I'd rather just cider-find-var, glance at it, and jump back with one press of a binding. Suggestions?
M-, should be emacs default shortcuts to navigate back and forth in any particular mode that supports that notion. CIDER follows that convention
well, I don't get any search engine use and/or documentation review awards today.
also i like a forum for otherwise easily googleable answers sometimes. it might take you 10 minutes to find it, but if you just ask someone can answer in 2 seconds.
well, I appreciate it! I just managed to rebind M-. from the default evil-mode binding... one last tweak would be nice (a -very- minor one without which I can live with, for sure): when I press M-. (now bound to cider-find-var) with the pointer over a symbol I am prompted in the minibuffer with 'Symbol (default find-title):' and then have to to press Enter... is this your behavior? I'd rather just jump to the definition right away.
those bindings had been absconded with by another mode, so I was not aware of them.
re: asking for symbol versus just doing it, check out:
(defun cider-prompt-for-symbol-function (&optional invert) "Prompt for symbol if funcall `cider--should-prompt-for-symbol' is truthy. Otherwise attempt to use the symbol at point for the command, and only prompt if that throws an error. INVERT is used to invert the semantics of the function `cider--should-prompt-for-symbol'." (if (cider--should-prompt-for-symbol invert) #'cider-read-symbol-name #'cider-try-symbol-at-point))
where would you put that... in your init.el, or the cider source, or somewhere else?
I apparently have cider in both elpa and package in my .emacs.d... not sure which is being loaded, lol.