emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#19242: closed (latest grep considers text files as


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#19242: closed (latest grep considers text files as binary)
Date: Mon, 01 Dec 2014 22:43:01 +0000

Your message dated Mon, 01 Dec 2014 14:41:53 -0800
with message-id <address@hidden>
and subject line Re: latest grep considers text files as binary
has caused the debbugs.gnu.org bug report #19242,
regarding latest grep considers text files as binary
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
19242: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19242
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: latest grep considers text files as binary Date: Mon, 01 Dec 2014 18:05:51 +0100 User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
Since grep 2.21, grep fails to report matches in a UTF-8 file with a few
non-UTF-8 bytes interspersed. This is likely to be related to one of the
recent patches related to encoding or multi-byte issues I see in the change log.

I have a number of large UTF-8 source files with some non-UTF-8 characters
used as constants and it was quite useful that grep nonetheless would
simply report the requested matches. Now it claims just
"Binary file ... matches" even if the file contains only one single
non-UTF-8 byte which I consider quite inappropriate.
I would appreciate to get the previous behaviour restored, at least in a
UTF-8 locale, as the mentioned patches are apparently intended to fix
issues in non-UTF-8 locales.

Kind regards,
Thomas

--- End Message ---
--- Begin Message --- Subject: Re: latest grep considers text files as binary Date: Mon, 01 Dec 2014 14:41:53 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
Also marking Bug#19242 as done, since it's the same as Bug#19241.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]