Re: Bash-3.1 official patch 7
On Sun, Feb 05, 2006 at 01:38:47PM -0500, Chet Ramey wrote: >BASH PATCH REPORT >= > > Bash-Release: 3.1 > Patch-ID: bash31-007 > > Bug-Reported-by: Tim Waugh <[EMAIL PROTECTED]>, Laird Breyer <[EMAIL > PROTECTED]> > Bug-Reference-ID: <[EMAIL PROTECTED]> This is great -- now the segfaults are gone. Unfortunately, the original job handling bug I reported still remains. Some exit codes are being reported incorrectly when a process uses a PID that bash has seen before. Tim. */ pgpBKVR3rY4Z8.pgp Description: PGP signature ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Bash-3.1 official patch 7
Tim Waugh wrote: > Unfortunately, the original job handling bug I reported still > remains. Some exit codes are being reported incorrectly when a > process uses a PID that bash has seen before. Of course -- this patch did not address that problem. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.case.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
one by one undo the undos
We see: (C-_, C-x C-u) Incremental undo, separately remembered for each line. Each line? Fancy. I'd trade it for a way to back out once one has undone too much. Like real emacs, one can do e.g., ^F to break the undo "habit" and then begin undoing the undos. With bash there is no way but to continue undoing, continue the destruction. Other approach: gimp has a redo key. We see: revert-line (M-r) Undo all changes made to this line. This is like executing the undo command enough times to return the line to its initial state. Thanks but all I wanted to do was undo one undo... ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
