From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: recursive query replace regexp
Date: Tue, 14 Jan 2003 16:26:55 +0100 [thread overview]
Message-ID: <84lm1nah1c.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: b010tv$fb6$1@mercur.foa.se
"Per Nordlöw" <per@foi.se> writes:
> Is there any way to perform an interactive replace (query-replace) of
> regular expressions recursively in all or some (specified by a regular
> expression) files present in a directory tree.
In addition to TAGS files, another approach is M-x find-dired RET to
generate a dired buffer with the files, then invoke Q (not q).
You need (require 'dired-x) in ~/.emacs for Q to work.
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-14 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 12:49 recursive query replace regexp Per Nordlöw
2003-01-14 13:34 ` Christopher J. White
2003-01-14 15:26 ` Kai Großjohann [this message]
2003-01-14 21:15 ` kgold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84lm1nah1c.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).