From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: query-replace / occur on multiple buffers
Date: 24 Mar 2004 13:20:21 +0200 [thread overview]
Message-ID: <uhdwea3uy.fsf@elta.co.il> (raw)
In-Reply-To: <Pine.LNX.4.56.0403240930000.588@z1sys.com> (message from Antanas Masevicius on Wed, 24 Mar 2004 09:31:52 +0200 (EET))
> Date: Wed, 24 Mar 2004 09:31:52 +0200 (EET)
> From: Antanas Masevicius <antanas.masevicius@z1sys.com>
>
> and what could be solution for replacement in certain directory?
> Is there any standard function?
See the node "Operating on Files" in the Emacs manual: it describes a
Dired command bound to the `Q' key that does this.
next prev parent reply other threads:[~2004-03-24 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 2:45 query-replace / occur on multiple buffers exits funnel
2004-03-23 18:56 ` Carsten Weinberg
2004-03-24 7:31 ` Antanas Masevicius
2004-03-24 11:20 ` Eli Zaretskii [this message]
2004-03-24 11:25 ` Emory Smith
2004-03-25 13:55 ` Antanas Masevicius
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=uhdwea3uy.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=eliz@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).