Ken Moffat wrote:
On Mon, Feb 15, 2016 at 04:07:58PM -0600, Bruce Dubbs wrote:
I do subscribe to the grep mailing list. There was a change in 2.23 that
IIRC was related to this. What I see as the problem is the line:
/usr/share/doc/kbd-2.0.3/utf/<E2><99><AA><E2><99><AC>
Yes, I noticed that, but compared to the more urgent problem it
seemed unimportant. <sigh/>
What happens if you prefix your grep commands with LC_ALL=en_US.utf8?
Or the GB equivalent.
Seems to work for me. So 'grep -v' in the C or POSIX locales is
failing badly, but ok in utf8 locales.
Possibly from that UTF-8 kbd file. If I only run it in e.g. /bin
the C version works fine, so it seems that it falls over at
characters which cannot be correctly processed in the current
locale.
That's the intended behavior of grep. How would it know if the line
matched or not?
My logs from gzip and iproute2 are correct, so it was indeed kbd
which broke my logging with this version of grep.
Well that's solved then. Good.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
