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: <5.1.0.14.2.20020727081951.02b14558@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Sat, 27 Jul 2002 08:32:02 -0700
To: Cygwin Discussion <cygwin AT cygwin DOT com>
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: RE: bash and the delete key
In-Reply-To: <20020727150640.1691.qmail@web21005.mail.yahoo.com>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020726221514 DOT 03f37468 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Nicholas,

At 08:06 2002-07-27, Nicholas Wourms wrote:
>--- Randall R Schulz <rrschulz AT cris DOT com> wrote:
> > >So I ask again, is remapping CTRL-V going to cause any problems
> > >for those who have no desire to enter tabs on the command line?
> >
> > For the ignorant, no, it will cause no problems. For those who need 
> literal
> > next and have the legitimate expectation that it will be in the default
> > place (CTRL-V), yes it matters and should not be changed.
>
>I would like to point out that CTRL-V is used by nano and pico users
>to scroll down one page.  If I'm not mistaken, it is used in lynx as
>well.  In fact, pretty much any readline based application I can
>think of uses it.  Since readline uses inputrc for its bindings, this
>would probably break the binding in many current applications.  I
>have to agree with Randall that this would be a very bad idea, and
>probably cause many mailing-list headaches (as most newbies like to
>use pico/nano).  If I know Chris' responses, he'd probably say
>something like, "Hell will freeze over first before CTRL-V gets
>changed."  Either that, or "We aren't going to change it because we
>are *mean*."

Vi uses it as (surprise) literal-next.

Also, I conducted an experiment. I changed the tty driver's "lnext" 
character and launched a sub-shell (BASH), but in that shell even though 
the "stty -a" confirmed my change to "lnext" was still in effect, readline 
within BASH was still using CTRL-V as the literal next character. Further 
experimentation suggests that readline will only adapt to the tty driver's 
"lnext" character if it does not conflict with a pre-existing readline 
binding. In any case, it keeps CTRL-V as literal next even if the tty 
driver's "lnext" does not conflict.


>Sorry, it ain't gonna happen, 'Nuff Said.

One can only hope.

This whole business ain't as simple as it might seem, since so many 
characters are interpreted by the tty driver and / or readline and various 
applications.


>Cheers,
>Nicholas


Randall Schulz


--
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/