This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (10)
- # aws (10)
- # babashka (11)
- # beginners (77)
- # calva (9)
- # cider (10)
- # cljdoc (7)
- # cljs-dev (47)
- # clojure (47)
- # clojure-uk (4)
- # clojurescript (87)
- # community-development (15)
- # conjure (14)
- # core-async (25)
- # crux (22)
- # cursive (6)
- # fulcro (6)
- # helix (3)
- # joker (2)
- # nrepl (1)
- # off-topic (1)
- # pathom (9)
- # pedestal (6)
- # re-frame (22)
- # reitit (15)
- # shadow-cljs (26)
- # spacemacs (16)
- # testing (2)
- # tools-deps (12)
- # uncomplicate (10)
I'm an issue with debugging in Cider/Spacemacs. The Normal Mode keybindings seem to be overriding the Cider Debugger keybindings (n, i, e, etc.), exactly as described in https://github.com/syl20bnr/spacemacs/issues/2356. Anyone else have this problem?
@neil.hansen.31 Yes it seems the debugging menu wrapper function is not working completely in Evil state (not sure why the related commit doesnt work, needs some investigation).
One approach is to switch to Emacs state using
C-z and then the key presses will be that of the debug menu rather than Evil normal state.
C-z will toggle back to Evil when you are done.
\ key (in Spacemacs develop) which runs
evil-execute-as-emacs-state for the next key press, so if you just want to inspect a value,
@jr0cket Thanks so much, those are great suggestions. I didn't know those bindings existed at all. That gets me back to work for today. What's the best protocol to follow to report this to CIDER/Spacemacs? Should I comment on the issue I posted above, or re-open a new one?
SPC h I to report a bug from Spacemacs directly. This creates a new issue in the GitHub repository for Spacemacs. Then reference the original issue you posted in the GitHub description. It will be good to specify a reproduction guide as not all Spacemacs maintainers use Clojure (yet).
Its a strange bug as I find that keys
q correctly call the cider debug menu, however,
s call the Evil normal state commands instead.
I wrote a basic troubleshooting and reporting guide for Spacemacs - https://practicalli.github.io/spacemacs/install-spacemacs/troubleshooting.html
There is also a #spacemacs specific channel as well, although sometimes is not immediately clear if an issue is CIDER or Spacemacs.
I've read through pieces of your book @jr0cket, looks like I'll be going through page by page now to make sure I understand the fundamentals. It's an amazing resource, thanks for your work on it.