AshokEmrys / conque

code.google.com/p/conque
0 stars 0 forks source link

Control-W [direction] issues with set -o vi #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open VIM and run :ConqueTermVSplit bash.
2. Run "set -o vi" to enable VI keybindings in bash
4. Hit Escape.
5. Press Control-W l and observe that focus does not move to the right 
window as expected.  Instead, the cursor moves to the right within the 
ConqueTerm window.

If 5 does not demonstrate the error, try going in and out of insert mode 
near the first character of the line.

VIM 7.2 on Ubuntu 9.10.  Please let me know if you can't reproduce the 
issue, and don't burn lots of time trying.  It's only a minor nit.

Great, great piece of work, BTW.

Original issue reported on code.google.com by rhys.ule...@gmail.com on 19 Feb 2010 at 9:01

GoogleCodeExporter commented 8 years ago
I was unable to reproduce the issue, although I have a few ideas which may 
explain
this behavior.

I wanted to keep the <Esc> key for going in and out of insert mode, but this 
makes it
more difficult to pass the escape character to bash for line editing and such. 
To
pass an escape character to bash, you have to press <Esc> twice. Pressing it 
twice
will leave you in insert mode.

So, getting back to the issue at hand, it seems like two things could be 
happening here:

1. You pressed <esc> twice then <C-w>l, so the second command was sent to bash 
since
you never left insert mode.

2. On your keyboard or vim configuration, pressing <C-w>l sends an escape 
character
at the beginning of the expression. Typically <C-w> should send the ascii 
character
23, however is possible that your setup is sending <Esc>w instead. In the gnome 
shell
pressing <Alt>-w sends <Esc>w, but I've never seen it send the escape character 
for
control characters.

At any rate, some things to try would be:

1. Make sure you're not pressing <esc> twice by accident.
2. Make sure you don't have any special mappings which are interfering with 
<C-w>.

Thanks for the feedback,
Nico

Original comment by nicora...@gmail.com on 19 Feb 2010 at 11:12

GoogleCodeExporter commented 8 years ago
Thank you for the help.  Feel free to close this one.

Original comment by rhys.ule...@gmail.com on 19 Feb 2010 at 11:18

GoogleCodeExporter commented 8 years ago

Original comment by nicora...@gmail.com on 20 Feb 2010 at 12:29