> 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
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1535458

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed
Status in grep package in Debian:
  Fix Released

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
    $ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
    binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  
  This worked as expected before the upgrade from 15.04 and 15.10.

  
  This is a HUGE issue that makes it impossible to do everyday developing work.

  
  Until you fix it, please f***ing roll back grep to the previous version, 
because this sh** is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to