From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: incremental regexp replace
Date: Sat, 17 Jun 2006 03:39:18 +0200 [thread overview]
Message-ID: <yoiju06kblx5.fsf@linus003.dd.chalmers.se> (raw)
In-Reply-To: mailman.2959.1150506770.9609.help-gnu-emacs@gnu.org
"Ryan Krauss" <ryanlists@gmail.com> writes:
> If I use incremental regexp search as a way to figure out the
> correct syntax for my regexp, is there an easy way to copy that
> regexp into the kill-ring or something so that I can easily use it
> in a regexp replace operation?
M-e lets you manipulate the search string in a regular minibuffer.
In Emacs 22 (CVS) you can drop into query-replace directly:
*** M-% typed in isearch mode invokes `query-replace' or
`query-replace-regexp' (depending on search mode) with the current
search string used as the string to replace.
(from etc/NEWS)
(Setting `query-replace-interactive' to a non-nil value makes
query-replace always use the last search string.)
--
Johan Bockgård
next parent reply other threads:[~2006-06-17 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2959.1150506770.9609.help-gnu-emacs@gnu.org>
2006-06-17 1:39 ` Johan Bockgård [this message]
2006-06-17 1:12 incremental regexp replace Ryan Krauss
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=yoiju06kblx5.fsf@linus003.dd.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
/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).