GNU bug report logs - #68776
bug with escape characters in pattern

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 68776 in the body.
You can then email your comments to 68776 AT debbugs.gnu.org in the normal way.

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

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

From: Brendan Richardson <brichardson <at> brandeis.edu>
To: bug-grep <at> gnu.org
Subject: bug with escape characters in pattern
Date: Sat, 27 Jan 2024 19:00:37 -0500

[Message part 1 (text/plain, inline)]

Hello,

If you use input
egrep "[^\\n\\t]" file

and the file contains a line with only n or t on it, those lines are also
excluded
file
normal lines
tttttt
nnnnn



KR
Brendan Richardson

[Message part 2 (text/html, inline)]

Message #10 received at 68776-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Brendan Richardson <brichardson <at> brandeis.edu>
Cc: 68776-done <at> debbugs.gnu.org
Subject: Re: bug#68776: bug with escape characters in pattern
Date: Sun, 28 Jan 2024 18:35:35 -0800

On 2024-01-27 16:00, Brendan Richardson wrote:
> If you use input
> egrep "[^\\n\\t]" file
> 
> and the file contains a line with only n or t on it, those lines are also

This is the correct behavior. The command you mention is equivalent to

grep -E '[^nt\]' file

and this outputs all lines containing some character other than 'n', 
't', or '\'. A line containing only n or t should not be output.

Previous Next

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