On Sun 4-Feb-07 3:39pm -0600, A.J.Mechelynck wrote:
> I can't test Ctrl-Tab here because it's one of those keys
> which are preempted by the window manager (Ctrl-Tab and
> Ctrl-Shift-Tab cycle through virtual desktops the way
> Alt-Tab and Alt-Shift-Tab cycle through the open windows
> of the current desktop). Doesn't Vim see it as synonymous
> with Tab?
>
> Shift-Tab is a "meaningful" key (tab backwards) which is handled like
> non-printable keys (multibyte keyboard sequence dependent on the terminal).
> Vim can map such combos provided that it can see them.
Yes, in the Ctrl-V context, Ctrl-Tab behaves like Tab.
Ctrl-Shift-Tab, after Ctrl-V produces <C-S-Tab>.
Otherwise, Ctrl-Tab works fine. I use it regularly without
thinking about it. From my _vimrc:
nmap <silent> <C-Tab> <C-W>w
nmap <silent> <S-Tab> <C-W>W
> I don't know how TheBat! gets its special-key keyboard
> input (raw or cooked for instance). IIUC, Vim uses
> "cooked" keyboard input, which is more portable across
> platforms and keyboard layouts, but is less powerful for
> complex key combinations since there is an additional
> software layer between the keyboard hardware and the
> program -- and that can conceivably lead to loss of
> information if the user presses a key combo not foreseen
> (or discarded as "not meaningful") by the translation
> software. Rather than a "bug", I would call it a
> "limitation" of the way Vim gets its keyboard input.
I agree that its more of a limitation than a bug. It's too
bad - I start Gvim with go=M so I see no GUI stuff and work
with just the keyboard. I find it easier to press a
modified keystroke (like Alt-Ctrl-k or Ctrl-Shift-k) then
multiple keystrokes (like <leader>k). Plus it gives us far
more single keystroke commands (eight per key).
--
Best regards,
Bill
