@jessejanderson: good point about easy-motion-redux. Word indeed makes more sense
I'll check
for the cursor, it has been like this the entire time. Plan was to completely change the cursor when inside a proton command chain (different, color, make it bigger, I don't know) but noone did it yet
Huh, strange, I wonder why I never noticed before.
What’s the reason for it?
When you hit space, to make sure that all keystrokes are only captured by proton and not by other plugins, proton modifies the class list of the editor and removes vim-mode. Without that class the cursor changes back to insert like vim-mode isn't installed at all
when the proton-chain is over, proton re-adds the vim-mode class
if you want to style the cursor, use the .proton-mode
selector
gotcha, coo make sense
guys what do you think, does it make sense to have a timeout on which-key
after it is already visible?
Default behaviour:
1. space
2. <timeout>
3. which-key shows
4. hit w
5. <timeout>
6. w
menu shows
you can toggle that but I want to get rid of 5. completely
the initial timeout I understand but is there any scenario where you want a timeout between commands to reflect in the UI?
@dvcrn seems sensible to me! 👍