From: Alan <wehmann@fnal.gov>
To: help-gnu-emacs@gnu.org
Subject: Re: Resume-ing a query-replace
Date: Sat, 1 Jun 2013 06:43:26 -0700 (PDT) [thread overview]
Message-ID: <3eb6e12f-843b-46fb-8196-533f035d5d05@googlegroups.com> (raw)
In-Reply-To: <cae95c07-b54c-4f55-ac8a-3ef9eaea1bb9@d8g2000pbe.googlegroups.com>
On Thursday, May 30, 2013 10:35:20 AM UTC-5, gentsquash wrote:
> The doc for `dired-do-query-replace-regexp' has
>
>
>
> "...If you exit (C-g, RET or q), you can
>
> resume the query replace with the command M-<."
>
>
>
> Is there a version of `query-replace-regexp' with that same
>
> "resume" feature? [Possibly bound to a different key]
>
>
>
> -Jonathan
Have you considered command "repeat-complex-command"?
next prev parent reply other threads:[~2013-06-01 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 15:35 Resume-ing a query-replace gentsquash
2013-06-01 13:43 ` Alan [this message]
2013-06-02 11:41 ` Tim Visher
[not found] ` <mailman.865.1370173309.22516.help-gnu-emacs@gnu.org>
2013-06-04 16:06 ` gentsquash
2013-06-04 16:48 ` Tim Visher
2013-06-05 3:31 ` Alan
2013-06-05 12:10 ` Tim Visher
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=3eb6e12f-843b-46fb-8196-533f035d5d05@googlegroups.com \
--to=wehmann@fnal.gov \
--cc=help-gnu-emacs@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).