-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get back to normal mode when using vim visual mode if I don't yank anything except with q #35
Comments
Your step 2 is inconsistent with your In step 5 you mention writing something down but you cannot write while grabbing. Step 7 works for me: it clears the selection and lets me move cursor without selecting. Pressing If you want to quit the grabber and give control to the shell or whatever application you’re running, you need to press the key bound to If you want to quit the grabber with |
Hi! Thanks for replying!
Yes, that's right, I meant
I meant writing something down to select later, just because, but not while grabbing, as you said.
Oh! I see, thanks! Is there any way to make |
How is that different from just quitting? |
I don't know, I've just met this extension, but if none, then I guess I can get the behavior by just commenting the Escape mapping as you said above, right? |
Try and see if it matches your expectations? I don’t use vim bindings myself, for me Shift+arrows and Alt+arrows are more natural, so I don’t really know what vim users want. |
Sorry to open a new issue again, but this is a real one. For some reason, I can't escape to normal mode using the
Escape
keySteps to reproduce:
~/.config/kitty
mv ~/.config/kitty/kitty_grab/grab.conf.example ~/.config/kitty/grab.conf
echo "map f4 kitten kitty_grab/grab.py" >> ~/.config/kitty/kitty.conf
F4
v
to get into visual mode (move and/or select text if you want)Escape
to get out of visual mode.You can't get out except if we yank some text or press
q
(which shouldn't because it is commented by default).[
doesn't work either.Just to confirm, this is shown in the
grab.conf
file:The text was updated successfully, but these errors were encountered: