bug#22144: --exclude no longer works against arguments with a directory name

On 2015-12-11 19:31:46 -0800, Paul Eggert wrote: > On 12/11/2015 05:56 PM, Vincent Lefevre wrote: > >or --exclude, the description is clear: > > The description changed in grep 2.22, to match the 2.22 (also, > 2.6-and-earlier) behavior. My quote was from the grep 2.22 description (grep 2.22-1 Deb

bug#22181: endless loop in grep 2.22

Hello, I hit an endless loop in grep 2.22. I can reproduce it with # grep -obUa -P '\x04\x08\x00profile\x00\x07' cache--usr.sbin.smbldap-useradd 16profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profile 27801profi

bug#22144: --exclude no longer works against arguments with a directory name

Vincent Lefevre wrote: For the "main case", is this the canonical name as returned by realpath? I don't see why. grep doesn't need to compute anything's realpath.

bug#22144: --exclude no longer works against arguments with a directory name

On 2015-12-15 15:27:27 -0800, Paul Eggert wrote: > Vincent Lefevre wrote: > >For the "main case", is this > >the canonical name as returned by realpath? > > I don't see why. grep doesn't need to compute anything's realpath. How is the file name defined, then? -- Vincent Lefèvre - Web:

bug#22144: --exclude no longer works against arguments with a directory name

Vincent Lefevre wrote: How is the file name defined, then? It's built as a string, which is passed to 'open' without worrying about realpath. By the way in case it's not already clear, I agree with you that the current behavior is not good, it's just that we can't simply revert (as that was