proton

https://github.com/dvcrn/proton
dvcrn 2016-07-13T01:29:22.000185Z

@jessejanderson: good point about easy-motion-redux. Word indeed makes more sense

dvcrn 2016-07-13T01:29:36.000186Z

I'll check

dvcrn 2016-07-13T01:30:13.000187Z

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

2016-07-13T01:35:32.000188Z

Huh, strange, I wonder why I never noticed before.

2016-07-13T01:36:02.000189Z

What’s the reason for it?

dvcrn 2016-07-13T01:42:54.000190Z

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

dvcrn 2016-07-13T01:43:10.000191Z

when the proton-chain is over, proton re-adds the vim-mode class

dvcrn 2016-07-13T01:43:30.000192Z

if you want to style the cursor, use the .proton-mode selector

2016-07-13T01:45:56.000193Z

gotcha, coo make sense

dvcrn 2016-07-13T02:05:36.000194Z

guys what do you think, does it make sense to have a timeout on which-key after it is already visible?

dvcrn 2016-07-13T02:06:56.000195Z

Default behaviour: 1. space 2. <timeout> 3. which-key shows 4. hit w 5. <timeout> 6. w menu shows

dvcrn 2016-07-13T02:07:06.000196Z

you can toggle that but I want to get rid of 5. completely

dvcrn 2016-07-13T02:07:42.000197Z

the initial timeout I understand but is there any scenario where you want a timeout between commands to reflect in the UI?

2016-07-13T11:20:37.000198Z

@dvcrn seems sensible to me! 👍