Fork me on GitHub
#proton
<
2016-07-13
>
dvcrn01:07:22

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

dvcrn01:07:36

I'll check

dvcrn01:07:13

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

jessejanderson01:07:32

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

jessejanderson01:07:02

What’s the reason for it?

dvcrn01:07:54

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

dvcrn01:07:10

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

dvcrn01:07:30

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

jessejanderson01:07:56

gotcha, coo make sense

dvcrn02:07:36

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

dvcrn02:07:56

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

dvcrn02:07:06

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

dvcrn02:07:42

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

tgg11:07:37

@dvcrn seems sensible to me! 👍