Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <01a701c2868d$e71fd910$b001a8c0@coosbayreza>
From: "Reza Roodsari" <rroodsari AT osatechnologies DOT com>
To: <cygwin AT cygwin DOT com>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106131511 DOT 0212e850 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106151936 DOT 01febb78 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106163952 DOT 02068e70 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106181835 DOT 02a5b3c0 AT pop3 DOT cris DOT com> <20021107024215 DOT GA16492 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106191839 DOT 02b745e0 AT pop3 DOT cris DOT com> <20021107033609 DOT GA15105 AT redhat DOT com> <20021107081133 DOT G2180 AT cygbert DOT vinschen DOT de> <20021107153318 DOT GA27471 AT redhat DOT com> <20021107165659 DOT B24497 AT cygbert DOT vinschen DOT de> <20021107160635 DOT GD28177 AT redhat DOT com>
Subject: Re: Problem with function keys codes with vt100 emulation
Date: Thu, 7 Nov 2002 10:45:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

Hi Christopher,

First, thanks to you and Randall, I now understand the issue and have made
my peace with the reported problem.

This email is about your expressed opinion that the cygwin key bindings
could have been better than they currently are.  I have been thinking about
what you are saying, and it seems to me that this is very much like the <LF>
vs. <CR><LF> issue.  No choice is right for every situation and there will
always be people with strong opinions on both side.  That's why cygwin
handles it the way it does - "you, the people, get a choice".  And now
everyone is happy (or at least fully responsible for the results they get).

It occurred to me that the cygwin console, being that it is fathered by Unix
but lives in the house of Windows, could suffer from the same
multiple-personality disorder.  So one way out would be to make the terminal
emulation choice an install time option.  This would keep you backward
compatible and also give you a 2nd shot at trying something totally new,
like the new key bindings.

As a side benefit, it may solve my problem too :-)

Regards,

Reza

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Thursday, November 07, 2002 8:06 AM
Subject: Re: Problem with function keys codes with vt100 emulation


> On Thu, Nov 07, 2002 at 04:57:00PM +0100, Corinna Vinschen wrote:
> >On Thu, Nov 07, 2002 at 10:33:18AM -0500, Chris Faylor wrote:
> >>On Thu, Nov 07, 2002 at 08:11:33AM +0100, Corinna Vinschen wrote:
> >>>On Wed, Nov 06, 2002 at 10:36:09PM -0500, Chris Faylor wrote:
> >>>>I see what I was missing.  F1 == ^[[[A, Up arrow == ^[[A.  F1 has one
> >>>>extra bracket.
> >>>>
> >>>>I think this is also kind of lame but changing it now would probably
> >>>>break too many things.  I'd like to make it the same as termcap but
> >>>>it's too late now.
> >>>
> >>>What's the problem?  It's the same sequence produced by the linux
> >>>console.
> >>
> >>The linux console is lame.
> >
> >The windows console is lame, too.  So it should be ok.
>
> Unfortunately, I don't have the source to the windows console.  I do
> have the source to the cygwin console and I am distressed to see that
> someone could have used better emulation for the function keys in cygwin
> but chose not to.  If I didn't think that many people were relying on
> the current behavior, I would change it.
>
> Why are we having this discussion again?
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/