bug#68776: closed (bug with escape characters in pattern)

[GNU bug Tracking System]

Your message dated Sun, 28 Jan 2024 18:35:35 -0800
with message-id <325fad6c-cc51-4cf9-ab8a-55d6f57c8635@cs.ucla.edu>
and subject line Re: bug#68776: bug with escape characters in pattern
has caused the debbugs.gnu.org bug report #68776,
regarding bug with escape characters in pattern
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
68776: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68776
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: bug with escape characters in pattern Date: Sat, 27 Jan 2024 19:00:37 -0500

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

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#68776: bug with escape characters in pattern
>
>
>
>
> Date: 
>
> Sun, 28 Jan 2024 18:35:35 -0800
>
>
>
>
> User-agent: 
>
> Mozilla Thunderbird
>
>
>
>
> 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.
>
>
> --- End Message ---