On Fri, Jun 20, 2008 at 12:17:30PM +0200, Thorsten Kampe wrote:
>The question is why you do have different actions for those in Cmd
>(which uses the same Windows terminal). Maybe because Cmd does not use
>the same "keycode" mechanism as the Unix terminal/shells. But that's all
>more or less gues
* Frank Jacobs (Thu, 19 Jun 2008 09:51:00 -0500)
> > Because Windows Console returns the same keycode for shifted/
> > unshifted and for the Ctrl key. You can easily test that with
> > [Ctrl][V] or "od -c" (which are the standards tools to find out the
> > key codes to be able to assign actions to
> Because Windows Console returns the same keycode for shifted/
> unshifted and for the Ctrl key. You can easily test that with
> [Ctrl][V] or "od -c" (which are the standards tools to find out the
> key codes to be able to assign actions to them).
Thanks. Yeah, I do notice that "od -c" yields di
* Frank Jacobs (Tue, 17 Jun 2008 14:49:18 -0500)
> I've used the solution below so that I can go back in the completion
> list in Bash via the SHIFT-TAB keystroke. However, I can only get it
> to work when running in an xterm window (where $TERM=xterm). It
> doesn't work in the plain-ol' Windows co
* Frank Jacobs (Tue, 17 Jun 2008 14:49:18 -0500)
> I've used the solution below so that I can go back in the completion
> list in Bash via the SHIFT-TAB keystroke. However, I can only get it
> to work when running in an xterm window (where $TERM=xterm). It
> doesn't work in the plain-ol' Windows co
5 matches
Mail list logo
