toggling between normal and evilified state

[ghost]

Just for you @StreakyCobra 🐍

Description

org-agenda is toggling between evil-normal-state and evil-evilified-state

Reproduction guide

• Start Emacs
• M-x org-agenda
• hit evil-escape-key-sequence
• watch minibuffer to change state

Observed behaviour:
I observe org-agenda is changing to evil-evilified-state for no reason.

Expected behaviour:
I expect org-agenda to not switch to evil-evilified-state at all.

System Info

• OS: gnu/linux
• Emacs: 24.5.1
• Spacemacs: 0.105.9
• Distribution: Arch x86_64
• Layers:

     auto-completion
     emacs-lisp
     git
     org
     syntax-checking
     version-control
     dockerfile
     finance
     colors
     emoji
     python
     django
     javascript
     restclient
     html
     php

Backtrace

no backtrace appeared

[StreakyCobra]

Have you updated your packages recently? Also, can you edit your issue with the information of this template? It will help us to help you :-)

For what I see, it seems that it's toggling between evil-normal-state and evil-evilified-state. But why, that's the question :-)

[Andre0991]

Isn't evilified the expected Evil state for org agenda? Did you mean that it's changing to normal? Or am I confusing things here?

[ghost]

@Andre0991 I dont know what the default state of org-agenda is. I only know it is toggling between 2 states.

[StreakyCobra]

Whenever I press the evil-escape-key-sequence it's leaving org-agenda, so I can't reproduce :-/

[ghost]

@StreakyCobra I just noticed the same problem in neotree.

[StreakyCobra]

@fx3O2 I can't reproduce it there too.

[TheBB]

I can reproduce.

[StreakyCobra]

@TheBB Can you try to change the evil-escape-key-sequence to something else, totally different from fd? In my case it's gq, if it may behave differently.

[d12frosted]

Is it still reproducible?

[ghost]

@d12frosted Yes, still reproducible! @TheBB told me how I can disable evil escape in the agenda

(setq-default evil-escape-excluded-major-modes '(org-agenda-mode))

[d12frosted]

@TheBB is it a non-fix with described workaround or should it be fixed? 😸

[TheBB]

I honestly am not sure but we can postpone it until or if we have a discussion on this behaviour in evilified state.