On Thu, 13 Nov 2003, parv wrote:
in message [EMAIL PROTECTED],
wrote Francisco J Reyes thusly...
Do we want something like:
grep -r string *.c
I do not know about anybody else, i myself like to keep the current
behaviour for -r option.
Several people have expressed a simmilar
On Thu, 13 Nov 2003, Kirk Strauser wrote:
Grep works perfectly in that respect, thanks - it's your understanding
that's a bit askew. Say you're in a directory with 'file1.c', 'file2.c',
'file3.c', etc. When you type:
grep -r 'string' *.c
your shell (*not* grep!) is expanding your
At 2003-11-17T17:41:27Z, Francisco Reyes [EMAIL PROTECTED] writes:
Thanks for shedding some light into this topic.
You bet.
-Z, --decompress
Decompress the input data before searching. This option is only
available if compiled with zlib(3) library
We could have said exactly the same
On Thu, 13 Nov 2003, Francisco Reyes wrote:
On Fri, 14 Nov 2003, JacobRhoden wrote:
No need to hack grep plese! just use -R (it appears the man page does not
document the -R function, but you need to use -R in grep for it to recurse.
-R == -r
That was mentioned in the previous emails.
On Thu, Nov 13, 2003 at 05:37:39PM -0500, Francisco Reyes wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
I get no files. However, if I go into one of the subdirectories and do a
plain grep string *.c then string is found on
--- Matthew Hunt [EMAIL PROTECTED] wrote:
On Thu, Nov 13, 2003 at 05:37:39PM -0500, Francisco Reyes wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
I get no files. However, if I go into one of the subdirectories and do
--- Matthew Hunt [EMAIL PROTECTED] wrote:
On Thu, Nov 13, 2003 at 05:37:39PM -0500, Francisco Reyes wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
I get no files. However, if I go into one of the
On Thu, Nov 13, 2003 at 02:55:34PM -0800, Chris Readle wrote:
You can also do this with something like:
ls -laR | egrep *.c
He's trying to search the contents of files for a string. Your
suggestion searches the directory listing (and not in a very useful way,
since *.c does not mean the
On Nov 13, Francisco Reyes wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
find . -name *.c -exec grep -li string {} \;
Dan
--
Dan Busarow 949 443 4172
Dana Point Communications,
On Thu, 13 Nov 2003, Dan Busarow wrote:
On Nov 13, Francisco Reyes wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
find . -name *.c -exec grep -li string {} \;
If there are a large number of files this will call grep
On Thu, 13 Nov 2003, Matthew Hunt wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
I get no files. However, if I go into one of the subdirectories and do a
plain grep string *.c then string is found on several files.
When
On Thu, 13 Nov 2003, Viktor Lazlo wrote:
If there are a large number of files this will call grep numerous
times--it would be more efficient to pass to xargs so grep is only called
a few times:
find . -type f -print | xargs grep options string
Although in my case the files are few I will
in message [EMAIL PROTECTED],
wrote Francisco J Reyes thusly...
Do we want something like:
grep -r string *.c
I do not know about anybody else, i myself like to keep the current
behaviour for -r option.
If I get someone to change grep anyone care to comment on whether
it would be difficult
On Fri, 14 Nov 2003 02:37 pm, Francisco Reyes wrote:
On Thu, 13 Nov 2003, Matthew Hunt wrote:
The man page for grep says to use -r to recurse, yet when I try
something like
grep -r -li string *.c
I get no files. However, if I go into one of the subdirectories and do
a plain
On Fri, 14 Nov 2003, JacobRhoden wrote:
No need to hack grep plese! just use -R (it appears the man page does not
document the -R function, but you need to use -R in grep for it to recurse.
-R == -r
That was mentioned in the previous emails. It only recurses directories.
It will not work with
At 2003-11-14T03:42:18Z, Francisco J Reyes [EMAIL PROTECTED] writes:
I think I am going to research what would it take for someone to fix grep
and pay them.
Grep works perfectly in that respect, thanks - it's your understanding
that's a bit askew. Say you're in a directory with 'file1.c',
16 matches
Mail list logo
