grep aliases in .bashrc prevent use of extra flags in Ubuntu

grail · 04-20-2011, 01:26 AM

Well ... I am now officially confused :$

I have replicated David's tree from last post and executed all commands in the same order and my CLFS based system is getting different results

In fact, they are the expected results that the OP was looking for, I believe???

Code:

$ grep -rli 'foo' *
foofile-lvl1.sh
foofile-lvl1.txt
lvl2/foofile-lvl2.sh
lvl2/lvl3/foofile-lvl3.sh
lvl2/lvl3/foofile-lvl3.txt
lvl2/foofile-lvl2.txt
lvl2a/foofile-lvl2a.sh
lvl2a/lvl3a/foofile-lvl3a.sh
lvl2a/lvl3a/foofile-lvl3a.txt
lvl2a/foofile-lvl2a.txt

$ grep -rli 'foo' .
./foofile-lvl1.sh
./lvl2/foofile-lvl2.sh
./lvl2/lvl3/foofile-lvl3.sh
./lvl2/lvl3/foofile-lvl3.txt
./lvl2/foofile-lvl2.txt
./foofile-lvl1.txt
./lvl2a/foofile-lvl2a.sh
./lvl2a/lvl3a/foofile-lvl3a.sh
./lvl2a/lvl3a/foofile-lvl3a.txt
./lvl2a/foofile-lvl2a.txt

$ grep -rli --include='*.txt' 'foo' *
foofile-lvl1.txt
lvl2/lvl3/foofile-lvl3.txt
lvl2/foofile-lvl2.txt
lvl2a/lvl3a/foofile-lvl3a.txt
lvl2a/foofile-lvl2a.txt

$ grep -rli --include='*.txt' 'foo' .
./lvl2/lvl3/foofile-lvl3.txt
./lvl2/foofile-lvl2.txt
./foofile-lvl1.txt
./lvl2a/lvl3a/foofile-lvl3a.txt
./lvl2a/foofile-lvl2a.txt

$ grep -rli --include='*.txt' 'foo' . ./lvl2/lvl3/foofile-lvl3.sh
./lvl2/lvl3/foofile-lvl3.txt
./lvl2/foofile-lvl2.txt
./foofile-lvl1.txt
./lvl2a/lvl3a/foofile-lvl3a.txt
./lvl2a/foofile-lvl2a.txt

So apart from different sorting, I seem to only be getting txt files when using --include
and I am not getting any exclusions???

David the H. · 04-20-2011, 01:48 PM

Found it. The include=exclude thing's a bug. And it's been fixed, at least in any distro that's up-to-date. Which of course doesn't include Debian, which is still using version 2.6.3.

http://savannah.gnu.org/bugs/index.php?29876

I wonder if that's what's affecting the processing order too?

sneakyimp · 04-20-2011, 01:50 PM

You guys are hard-core!

I agree that exclusion of files that match your --include filter in the top-level directory is totally, completely bizarre. I assert once again this is NOT how grep behaves on other machines. I just performed this command on a CentOS 5 machine and the results included numerous php files in the top-level directory:

Code:

grep --include=*.php -irl 'adams' *

I can deal with typing a period instead of a wildcard every time, what's worrisome to me is that Ubuntu 10 is behaving differently than CentOS 5 (and various debian distros as well AFAIK).

sneakyimp · 04-20-2011, 01:51 PM

Quote:

Originally Posted by David the H.

Found it. The include=exclude thing's a bug. And it's been fixed, at least in any distro that's up-to-date. Which of course doesn't include Debian, which is still using version 2.6.3.

Nice work. Do you have to upgrade linux kernel to fix the bug or it some other library?

David the H. · 04-20-2011, 02:07 PM

It's a bug in grep, so you simply need to upgrade grep.

2.6.3, and perhaps other 2.6 releases, show the problem. The newest version, 2.7, as well as 2.5.4 and before appear to be ok, according to the bug report.

If you can survive it, just wait for your distribution to do it. They'll get around to upgrading the package eventually. If you really need this feature right away, you'll have to download the source from gnu and compile it yourself.

ftp://ftp.gnu.org/gnu/grep/

grail · 04-20-2011, 07:42 PM

Thanks David ... that would explain it as my CLFS system is fairly bleeding edge