Doesn't play well with evil-snipe

[NightMachinery]

evil-snipe overrides 's', and so 's' doesn't activate stacktrace when debugging.

[bbatsov]

That's not really a CIDER issue. evil-snipe (and similar modes) should be careful with what their binding/changing in special modes.

[NightMachinery]

@bbatsov What can be done to fix the issue, presumably on evil-snipe's side?

[NightMachinery]

@bbatsov I tested edebug, and it had no issues with evil-snipe ('s' ran edebug-step-mode when edebug was active.).

[NightMachinery]

@bbatsov From evil-snipe:
I'm not familiar with CIDER's debugger, but you can prevent evil-snipe from being enabled in certain major modes by adding it to evil-snipe-disabled-modes, or by adding turn-off-evil-snipe-mode to the appropriate hook. e.g.

;; NOTE: I'm guessing the major mode and hook names
(push 'cider-debug-mode evil-snipe-disabled-modes)
;; or
(add-hook 'cider-debug-mode-hook #'turn-off-evil-snipe-mode)

If you tell me what the appropriate major-mode is, I'll be happy to add it to evil-snipe-disabled-modes's default.

[bbatsov]

It's a minor mode actually - cider--debug-mode.

[NightMachinery]

The hook cider--debug-mode-hook runs both when entering and leaving debug mode. How do I differentiate between these two to disable/enable evil-snipe?

[NightMachinery]

Nevermind, I found the answer:

(add-hook 'cider--debug-mode-hook (lambda ()
                                      (if (bound-and-true-p cider--debug-mode)
                                          (turn-off-evil-snipe-mode)
                                        (turn-on-evil-snipe-mode))))

[bbatsov]

Great! Guess we can close this then.