-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pressing <Esc> should not move the cursor if we're already in Normal mode #92
Comments
Please try the script from this repo, that should work. I will submit a PR to update the weechat script when I have some time :) |
Thanks, it works now as intended! |
Another question, not to open another issue, but when I'm in normal mode and I press <Esc> I would get back 1 character (like backspace). Can that be fixed? |
That's intended behavior (similar to vim). You can edit the source code if you don't like it, though. Specifically, you can comment out/remove this line. |
No, I mean when I'm in Insert mode and i press Esc it's normal to go back 1 character. |
Oh yeah, I'll reopen the issue and rename it so I don't forget about it. Thanks! |
Oh and something else (it may be related to mode switching): Pressing <Esc> to cancel Ex mode will erase current line. Steps to reproduce:
On further checking, the text is there if I press undo (u) and then redo (C-R). |
I am trying to reuse the normal keybindings for switching channels.
Normally, when pressing Ctrl+n I will advance one channel and Ctrl+p will go back.
Currently, this works only one I'm in Insert mode. When I switch to Normal mode it stops working.
I have tried the following nmaps:
And none worked.
I'm using the latest script on https://weechat.org/scripts/source/vimode.py.html/ : Version: 0.8.1
More info (I don't know if it helps):
:nmap
after setting the keybindings, I would not get the expected <C-n>, but only n or N or ^N.The text was updated successfully, but these errors were encountered: