GNU bug report logs - #23234
unexpected results with charset handling in GNU grep 2.23

Previous Next

Package: grep;

Reported by: Björn JACKE <bjoern <at> j3e.de>

Date: Wed, 6 Apr 2016 20:45:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Bjoern Jacke <bjoern <at> j3e.de>
To: Eric Blake <eblake <at> redhat.com>, 23234 <at> debbugs.gnu.org
Subject: bug#23234: unexpected results with charset handling in GNU grep 2.23
Date: Thu, 7 Apr 2016 00:23:53 +0200

On 06.04.2016 23:04, Eric Blake wrote:
> The change of treating encoding errors as binary files will NOT be
> reverted, but here,

hmm ... think of log files: In log files you will usually find all kind
of encodings. If a user greps for a certain error message string in a
log file he will not be able to find the errors because GNU grep will
terminate grepping as soon as the first byte which does not fit into the
locate encoding pops up. The only way would be to advice users to use
the C locale if that is the only one that will be fixed. I can't believe
that this is what you intended to achieve here.

And what about the output of "Binary file (standard input) matches" on
*stdout*? This is not distinguishable from a line that matched and
contains this text. How should a script catch this situation?

Björn
This bug report was last modified 9 years and 46 days ago.

Previous Next

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