Updated [experimental]: bash-3.1-8

Wells, Roger K. ROGER.K.WELLS@saic.com
Thu Sep 14 13:17:00 GMT 2006

Thank you.  You made me realize that I could modify .inputrc to cause Ctrl-l
to execute my version of "clear" which does what I want.  Now if I could do
it in Linux.......

Roger Wells, P.E.
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)

-----Original Message-----
From: ebb9@byu.net [mailto:ebb9@byu.net] 
Sent: Thursday, September 14, 2006 8:41 AM
To: cygwin@cygwin.com; Wells, Roger K.
Subject: Re: Updated [experimental]: bash-3.1-8

Hash: SHA1

According to Wells, Roger K. on 9/14/2006 6:29 AM:
> I applaud any effort to speed up bash but 3.1.18 immediately broke enough
> stuff that I do not believe we will proceed to use it in its present form.

bash 3.1.18 doesn't exist - the last official upstream patch for the 3.1
series was 17, so I just released 3.1.17, at packaging attempt 8.

> On my bash wish list I would include changing clear (ctrl-l) so that it
> clears the entire buffer and not just the lines that are currently
> I have the windows code to do this if any one wants to proceed.  I realize
> that the behavior is the same as it is in RedHat Linux where it produces
> same inconveniences.  Thus adopting this change would be a departure from
> other platforms.  Just a thought.

Huh?  bash-3.1-8 did not do anything differently than bash-3.1-6 in
regards to handling ctrl-l.  As for clearing the entire buffer vs. just
visible lines, that is a feature of what escape sequences your terminal
understands - which TERM are you using, cmd.com, rxvt, or xterm?  If it is
cmd.com, then the fix would be to cygwin proper, not bash (and even if
bash were involved, it would be readline, not bash).

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

More information about the Cygwin mailing list