From: Nelson Ferreira <nelson.ferreira@ieee.org>
Subject: Re: grep a string in different maps.
Date: Fri, 17 Nov 2006 20:12:15 -0500 [thread overview]
Message-ID: <m3hcwxeexc.fsf_-nfl---676e752e656d6163732e676e7573_---@tuxie.homelinux.net> (raw)
In-Reply-To: <1163757458.679316.268560@e3g2000cwe.googlegroups.com>
"william" == william a george <william.a.george@gmail.com> escreveu:
[...]
william> If I'm standing in the terminal directory then it is OK to find a
william> string among the files in "terminal", but if I want to find the string
william> when I'm standing in "SW" then it not possible. Grep cannot recurse
william> through the directories.
william> I tried this combination also: find . -name * -exec grep -n string NUL
william> {}
william> And I got a negative result too.
william> Can someone please help me to find a way to solve my problem?
In my setup, GNU grep supports the -r switch which does allow for
recursion.
I use it by M-x grep RET grep -rin string . RET
--
Nelson Ferreira
prev parent reply other threads:[~2006-11-18 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 9:57 william.a.george
2006-11-17 21:02 ` martin
2006-11-18 1:12 ` Nelson Ferreira [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hcwxeexc.fsf_-nfl---676e752e656d6163732e676e7573_---@tuxie.homelinux.net \
--to=nelson.ferreira@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).