From: Benjamin Rutt <rutt.4@osu.edu>
Subject: Re: replace a textblock in multiple files
Date: Tue, 26 Sep 2006 00:52:28 GMT [thread overview]
Message-ID: <87u02v1miu.fsf@penguin.brutt.org> (raw)
In-Reply-To: mailman.7384.1159203371.9609.help-gnu-emacs@gnu.org
<C.Strobl@dlr.de> writes:
> hello all,
> only a short and simple question: whats the best way to replace a
> textblock in multiple files.
> thanks and i hope the question is not to easy
> christian
M-x dired
mark desired files with 'm'
Q
--
Benjamin Rutt
next parent reply other threads:[~2006-09-26 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7384.1159203371.9609.help-gnu-emacs@gnu.org>
2006-09-26 0:52 ` Benjamin Rutt [this message]
2006-09-26 11:18 ` AW: replace a textblock in multiple files C.Strobl
2006-09-26 12:09 ` regexp question C.Strobl
2006-09-26 17:16 ` Peter Dyballa
2006-09-29 22:03 ` Dieter Wilhelm
2006-09-30 8:53 ` Peter Dyballa
[not found] ` <mailman.7422.1159272599.9609.help-gnu-emacs@gnu.org>
2006-09-27 7:58 ` Florian Kaufmann
2006-09-26 19:45 replace a textblock in multiple files Jay Bingham
-- strict thread matches above, loose matches on Subject: below --
2006-09-25 16:55 C.Strobl
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=87u02v1miu.fsf@penguin.brutt.org \
--to=rutt.4@osu.edu \
/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).