Updated [experimental]: bash-3.1-8
Thu Sep 14 12:40:00 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
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 visible.
> 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 the
> 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 firstname.lastname@example.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v220.127.116.11 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin