[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #25197] grep -R defaults to stdin, not the current directory
From: |
Geoffrey Thomas |
Subject: |
[bug #25197] grep -R defaults to stdin, not the current directory |
Date: |
Fri, 04 Dec 2009 22:58:38 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15 |
Follow-up Comment #4, bug #25197 (project grep):
Hi Paolo,
Just to clarify, the bug here is that grep -R should default to the current
directory if none is specified.
I'm okay with Apple's patch to warn but not change behavior as a compromise
if this behavior is somehow undesirable, but I don't see why it would be, and
I would expect lots of grep users to want this behavior -- there are multiple
people who found this ticket and voted in favor of it, for instance.
As another example, note that the git project's 'git grep' defaults to the
current directory without a '.' argument. I would imagine that Apple simply
didn't want to diverge so much from upstream, and took the conservative
approach.
Recursive grep of something that is not a directory (e.g., stdin) is
meaningless, so stdin is not a reasonable default for grep -R.
- Geoffrey
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25197>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/