GNU bug report logs - #21461
grep --color can leave terminal in weird state after signal

Previous Next

Package: grep;

Reported by: Paul Eggert <eggert <at> cs.ucla.edu>

Date: Fri, 11 Sep 2015 16:53:02 UTC

Severity: normal

To reply to this bug, email your comments to 21461 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-grep <at> gnu.org:
bug#21461; Package grep. (Fri, 11 Sep 2015 16:53:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Paul Eggert <eggert <at> cs.ucla.edu>:
New bug report received and forwarded. Copy sent to bug-grep <at> gnu.org. (Fri, 11 Sep 2015 16:53:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: grep bugs <bug-grep <at> gnu.org>
Subject: grep --color can leave terminal in weird state after signal
Date: Fri, 11 Sep 2015 09:51:47 -0700

If grep --color is interrupted, either via ^C or ^Z or some other signal, it can 
leave the output terminal in a weird state.  This problem was noted by Giuseppe 
Scrivano in <http://bugs.gnu.org/20062#143> and I'm forwarding the report here. 
 One fix would be to do what GNU 'ls' does; note that SIGTSTP must be treated 
specially so that the color state resumes after restart; also, the signal 
handler just sets a flag that is polled periodically by the main code.
This bug report was last modified 8 years and 237 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.