search

syl20bnr / evil-lisp-state

An evil state to navigate Lisp code and modify it with smartparens
GNU General Public License v3.0
91 stars 26 forks source link

Single key mappings not available in evil lisp state unless evil-lisp-state-global is set #37

Open bpstahlman opened 7 years ago

bpstahlman commented 7 years ago

My understanding from reading the doc string is that I should be able to execute evil-lisp-state commands using the leader specified with evil-lisp-state-leader as follows:

  1. if evil-lisp-state-global is t, in any major mode
  2. else in major modes listed in evil-lisp-state-major-modes

Moreover, I assumed that I would enter "lisp" state as follows:

  1. if evil-lisp-state-enter-lisp-state-on-command is t, upon executing any command with the leader
  2. else when I execute <leader> .

Finally, I assumed that once in "lisp" state, I should be able to execute commands using the short (generally single key, sans leader) keybindings. But what's confusing me is that even in "lisp" state, the leader key sequence is required unless I've set evil-lisp-state-global. Sure enough, code inspection revealed that evil-lisp-state-map is populated if and only if evil-lisp-state-global is t. I'm having trouble understanding the reason for this, especially given that the default setting of evil-lisp-state-enter-lisp-state-on-command is t. What's the point in a "lisp" state that doesn't give you more convenient (i.e., sans leader) access to the evil lisp state commands? Why wouldn't you populate evil-lisp-state-map (or even evil-lisp-state-local-map) unconditionally, and simply let evil-lisp-state-global determine where you can access the leader?

bpstahlman commented 7 years ago

@syl20bnr Is this project still actively maintained?