From: Hans-Christoph Wirth <hcw@despammed.com>
Subject: Re: combine isearch-forward-regexp and query-replace-regexp
Date: 10 Feb 2005 18:13:41 GMT [thread overview]
Message-ID: <slrnd0n92l.4m0.hcw@katla.informatik.uni-wuerzburg.de> (raw)
In-Reply-To: 877jlh43bx.fsf-monnier+gnu.emacs.help@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> Well you can either define this isearch M-% thingy (IIRC it was originally
> posted in this newsgroup before being integrated in Emacs-CVS), or you can
> go the low-tech route:
>
> C-s M-p C-k C-g
> M-% C-y
Thanks. This comes close to what I need. I made the mistake to leave
the initial isearch with C-g. When I leave it with RET, the contents
gets stored in the ring buffer, and can be invoked with M-p then.
prev parent reply other threads:[~2005-02-10 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 13:05 combine isearch-forward-regexp and query-replace-regexp Hans-Christoph Wirth
2005-02-08 14:15 ` Stefan Monnier
2005-02-09 14:07 ` Hans-Christoph Wirth
2005-02-09 14:25 ` Peter Dyballa
2005-02-09 18:09 ` Thien-Thi Nguyen
2005-02-10 1:23 ` Stefan Monnier
2005-02-10 18:13 ` Hans-Christoph Wirth [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
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=slrnd0n92l.4m0.hcw@katla.informatik.uni-wuerzburg.de \
--to=hcw@despammed.com \
/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).