This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-28
Channels
- # aleph (3)
- # babashka (66)
- # beginners (96)
- # calva (45)
- # clj-kondo (28)
- # clojure (30)
- # clojure-dev (2)
- # clojure-europe (20)
- # clojure-germany (22)
- # clojure-norway (4)
- # clojurescript (176)
- # clojutre (1)
- # cursive (23)
- # datalog (6)
- # datomic (7)
- # docker (3)
- # emacs (3)
- # exercism (4)
- # figwheel-main (5)
- # fulcro (8)
- # gratitude (9)
- # hyperfiddle (8)
- # introduce-yourself (2)
- # jobs (2)
- # malli (4)
- # membrane (3)
- # off-topic (17)
- # polylith (3)
- # portal (2)
- # re-frame (27)
- # reitit (3)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (152)
- # spacemacs (8)
- # tools-deps (15)
- # vscode (1)
- # xtdb (24)
A long shot but maybe someone here has an idea. This seems to be a particular problem with babashka nREPL+cider+evil-mode. When evaluating a form and it throws an error it'll pop up the *cider-error*
buffer as usual, but somehow it's not properly initialized. There's no syntax highlighting, no line numbers (I have global display-line-numbers-mode
on), and not all key bindings are present. The most annoying one is that pressing q
will do evil's macro record, instead of quit-window
. However doing pretty much anything (moving the cursor, switching to another buffer, doing M-x
, ...) will trigger the initialization. Suddenly syntax highlighting kicks in, line numbers are there, key bindings are installed... and this makes it really hard to debug, no matter what I try to inspect the state of the buffer undoes the problem I'm trying to diagnose... does this ring a bell to anyone?
maybe you can try toggle-debug-on-quit
, and try to press C-g right before syntax highlight and other things kick in, it should print a stacktrace where emacs stopped when you pressed C-g
If you find anything else on this, please post. I’m experiencing something similar with cider-inspect
and babashka