This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with function keys codes with vt100 emulation

On Wed, Nov 06, 2002 at 06:23:37PM -0800, Randall R Schulz wrote:
>At 18:07 2002-11-06, you wrote:
>>On Wed, Nov 06, 2002 at 04:50:12PM -0800, Randall R Schulz wrote:
>>>The terminal emulation available under Cygwin is not programmable, so it's
>>>up to the software to adapt to it, not vice versa.
>>I will note that it is very weird that F1 - F4 in cygwin are generating
>>the same sequences as up/down/left/right.  Something is messed up
>>somewhere, there.
>It would be weird if it were happening, but I have readline ("~/.inputrc") 
>mappings for all the Fn keys and "Insert" and "Delete" as well as the usual 
>pre-defined, built-in mappings for the arrow keys. Though I usually keep 
>NumLock engaged, the arrow keys on the number pad work fine when I 
>disengage it.

But, if you type F1 while you are in /bin/sh, you'll see the cursor move
up a line.  That indicates that cygwin is mapping F1 to ^[[A, which is,
AFAICT, incorrect.  It probably *should* be mapping to ^[OP.  And, F2
should be ^[OQ, etc.

I used to have these things memorized from my past life maintaining a text
editor (among other things).

Please do not send me personal email with cygwin questions or observations.
Use the resources at .

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]