This is probably somewhere lower in the system than vim, but I'm not sure where
to start looking, so I'm hoping I get lucky with ncurses.
In vim, ctrl-right arrow no longer operates as 'skip over the next word', but
now inserts 1;5c
The other arrow keys do the same thing for different codes.
In which terminal is this happening, in gnome-terminal?
gnome-terminal generates escape sequences that vim doesn't recognize, ^[O1;5D
^[O1;5C are generated for ctrl-left ctrl-right while in FC6 gnome-terminal it is
The wrong characters are also being sent when you use a terminal to ssh.
locally, ctrl-left skips over previous words in bash. but if you ssh somewhere
and try to do the same thing, you'll get ;5D printed out
This bug is *really* irritating, and should get fixed for F7 GA.
Yeah, this is a gnome-terminal bug. Ubuntu users have noted similar problems
because gnome-terminal has changed what sequences it outputs for various key
See the GNOME bug here: http://bugzilla.gnome.org/show_bug.cgi?id=425462
Created attachment 154303 [details]
Single-shift to G3 should not have modifier keys
Here's a patch that seems to work for me, based on the change to xterm
mentioned in the Gnome bug.
Based on the comments in the original gnome bug:
which was linked from the Ubuntu bug I mentioned:
this looks to be more of a vte bug than gnome-terminal. So I assume this is a
vte patch? I'll apply it and see how it works.
(In reply to comment #6)
> this looks to be more of a vte bug than gnome-terminal. So I assume this is a
> vte patch? I'll apply it and see how it works.
Yeah it is. I forgot to mention that part.
Having patched vte-0.16.3-2, ctrl-arrow works properly in vi/vim (yay!).
However, it still doesn't work right in irssi (boo!).
Also, shift-arrow causes bash to emit partial escape sequences, so we might need
to add some inputrc magic to handle the new stuff that vte is emitting.. but
that might be another bug.
(In reply to comment #8)
> Having patched vte-0.16.3-2, ctrl-arrow works properly in vi/vim (yay!).
> However, it still doesn't work right in irssi (boo!).
> Also, shift-arrow causes bash to emit partial escape sequences, so we might need
> to add some inputrc magic to handle the new stuff that vte is emitting.. but
> that might be another bug.
I'm not sure about irssi, but for bash i figure the problem is that the code I
wrote doesn't care if your in application mode or not, nor does it care if the
key pressed was a cursor key or not.
Please discuss upstream or your comments will be ignored.
The problem with irssi turns out to be an irssi bug, fixed upstream. With the
two current patches in the upstream bugzilla, ctrl-arrow works as expected in
(newer) irssi and vim, but not vim in a screen session. Alas.
Still, as long as vte behavior matches xterm's, anything else is an application
bug rather than a terminal bug.
This bug, while completely annoying, doesn't keep anyone from installing or
using their system. Moving to FC7Target.
It's irritating enough to have made me downgrade one machine back to FC6 though.
This really should get fixed for GA imo, or we'll have a lot of dupes of this
The upstream bug is fixed now.
Can someone check vte trunk and see if this is indeed fixed?
Is it ? The bugs seem to be still open.
A similar bug was fixed. GNOME bug 440475.
Sorry, meant GNOME Bug 375112 – ctrl-key combinations yielding just key
The bug is still there in vte 0.16.4
also still there in vte-0.16.6-1.fc7
It does seem to be fixed in rawhide however. Any chance of a backport?
(In reply to comment #20)
> and vte-0.16.8-1.fc7
> It does seem to be fixed in rawhide however. Any chance of a backport?
The difference between 0.16.8 and 0.16.9 that is in rawhide is really small. I
can't imagine how it could make the difference. I'm guessing that tother
software chaned in between fixing the issue. Anyway, pushing 0.16.9 in f7
Updates Testing, please test and let me know if it works.
You were right, upgrading vte to 0.16.9 in F7 doesn't solve the issue.
So, this bug has changed slightly. Initially, ctrl-arrow worked in bash, but
not in vim. Now in F8 the opposite is true.
ctrl-left prints ;5D
shift-left prints ;2D
alt-left prints ;3D
(In reply to comment #23)
> So, this bug has changed slightly. Initially, ctrl-arrow worked in bash, but
> not in vim. Now in F8 the opposite is true.
> in bash..
> ctrl-left prints ;5D
> shift-left prints ;2D
> alt-left prints ;3D
I'd check my bash settings, because it works fine here.
Yep. F8 works fine here. You've got TERM=xterm, right?
With no .bashrc (ie, just the F8 defaults). I still get the broken behaviour.
bash-3.2$ export | grep TERM
declare -x COLORTERM="gnome-terminal"
declare -x TERM="xterm"
Donno. What about a new account?
I just tried in a freshly installed F9beta, and it works fine.
Dave, problem solved for you ?
Declaring this fixed for now.
If you got anything new, just reopen.