URL:
<http://savannah.gnu.org/bugs/?32520>
Summary: If you use --include -- grep does not recurse all
subdirectires
Project: grep
Submitted by: keithwdaniels
Submitted on: Thu 17 Feb 2011 05:24:50 PM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
The testing below was based on the example
grep -rH --include='*.c' 'hello' /home/gigi"
from the grep 2.7 Info file.
I found two problems which I think are related:
Problem #1:
If you use --include grep does not recurse all subdirectories.
Converting the Info example above to my situation gives incomplete recursion
when this is run:
grep -rH --include='*.rc' 'extraToolBar' /home/$USER/.kde3/share
While this gives complete recursion when it is run:
grep -rH 'extraToolBar' /home/$USER/.kde3/share
Problem #2:
When specifying the path and globbing the file names the results appear to be
inconsistent. I would have expected
/home/$USER/.kde3/share/*.rc
to work and
/home/$USER/.kde3/share/ *.rc
NOT to work.
Instead....
Running this gives complete recursion:
grep -rH 'extraToolBar' /home/$USER/.kde3/share/*
Running this does not work at all:
grep -rH 'extraToolBar' /home/$USER/.kde3/share/*.rc
Running this gives complete recursion -- BUT -- gives the error message "grep:
*.rc: No such file or directory" at the end:
grep -rH 'extraToolBar' /home/$USER/.kde3/share/ *.rc
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32520>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
