This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-20
Channels
- # announcements (3)
- # babashka (7)
- # beginners (43)
- # biff (19)
- # calva (39)
- # cider (16)
- # clerk (2)
- # clj-yaml (32)
- # cljs-dev (37)
- # clojure (129)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (46)
- # clojure-filipino (1)
- # clojure-gamedev (25)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (2)
- # clojure-korea (1)
- # clojure-my (1)
- # clojure-nl (5)
- # clojure-norway (8)
- # clojure-sg (1)
- # clojure-sweden (12)
- # clojure-taiwan (1)
- # clojure-uk (9)
- # clojurescript (14)
- # core-typed (136)
- # cursive (18)
- # duct (9)
- # emacs (12)
- # etaoin (7)
- # events (1)
- # graalvm (3)
- # gratitude (2)
- # humbleui (7)
- # hyperfiddle (99)
- # introduce-yourself (5)
- # jobs (2)
- # leiningen (1)
- # missionary (14)
- # nrepl (2)
- # off-topic (12)
- # polylith (21)
- # rdf (29)
- # re-frame (8)
- # releases (1)
- # shadow-cljs (264)
- # spacemacs (21)
- # sql (7)
- # vscode (1)
A while ago cider/emacs stopped giving me as useful error notifications as it did before. I tried to debug my init.el
but couldn't find anything (I guess this is on the emacs side and not cider).
For example, evaluating
(defn foo [] undefined-thing)
creates a red line under the expression and jumps the marker to the start. However, there is no error information. I can see the error info in the repl buffer or by calling cider-jump-to-compilation-error
which shows it in the modeline:
Syntax error compiling at (dev/user.clj:37:1).
Unable to resolve symbol: undefined-thing in this context
but it used to show up as a nice popup right in the buffer. Is there a way to auto-call cider-jump-to-compilation-error
in this case, or get the window back? I really can't find what the issue is.There's defcustom cider-auto-jump-to-error
, default t
, perhaps you have it changed?
Besides from that, CIDER's 'jump to error' feature isn't as sophisticated as other of its error-related capabilities. It may or may not have to do with your problem.
(I actually have a wip branch for modernizing this feature)
If you create a GH issue, it sounds like we'll be happy to attend it when we have the chance.
I'd be happy to start an issue but I'll need to do some more digging first. Again, I'm sure this used to work sensibly, I just can't find what the issue is.
Could you create a detailed github issue? (and link to it so that Sam can also contribute any extra info) Thanks 🙂
Yeap; I’ll do that in the morning. This is on my work machine. I’m gonna nuke my packages and tweak some things because I’m having a ton of performance issues with LSP, and after I finish with that if the no error pop up is still happening I’ll create a ticket.
Any tips on integrating seancorfield’s `clj-new` deps-new
with emacs so I can, for example, do M-x clj-new
to create a new project without leaving emacs?
I know I could just use shell within emacs, but having a special function would be nicer.
https://github.com/jpe90/emacs-clj-deps-new is the emacs integration with clj-new and deps-edn projects by Sean Corfield