> I see, so I should use the "C" locale, > as that commonly means "I don't care about the encoding".
That is JUST A WORKAROUND that seems to work, but that shouldn't be needed. This is NOT the expected behavior. > I understand that grep works in another way now. Yeah, a wrong one because it has a bug. Which by the way appears to be fixed upstream. Note that grepping an ISO-8859-file (containing non-ascii characters) with an UTF-8 locale will usually *but not always* reproduce the issue, so the behavior is not even consistent or predictable. > one could say that it is more picky, but one could also consider this an improvement, NOPE NOPE NOPE > that the file warns, that the file is somehow 'non-standard' If the intent was to warn about something, the program would print a warning (and then do its job correctly). Treating the file as BINARY, when it is not, is not a sane way to "warn" about anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
