From: Drew Adams <drew.adams@oracle.com>
To: "Ben A." <ben.a@gmx.us>, Juri Linkov <juri@jurta.org>
Cc: Jambunathan K <kjambunathan@gmail.com>, 14979@debbugs.gnu.org
Subject: bug#14979: 24.3; Feature Request: query-replace-backward
Date: Sat, 3 Aug 2013 14:24:35 -0700 (PDT) [thread overview]
Message-ID: <5819bbc4-bf73-47a3-92e5-e4f7fde0cf55@default> (raw)
In-Reply-To: <87siyq8pxj.fsf@ThinkPad-W520.localdomain>
> > no prefix M-% - normal non-word replacement forwards
> > C-u M-% - word replacement forwards
> > M-- M-% (negative argument) - normal non-word replacement backwards
> > ??? - word replacement backwards
>
> no prefix M-% - normal non-word replacement forwards
> C-u M-% - word replacement forwards
> M-0 M-% - normal non-word replacement backwards
> M-- M-% - word replacement backwards
I vote against using a prefix arg for anything like this. There are
better things to use a prefix arg for.
Instead, either choose a different key altogether for backward q-r or
do not bind a key for it at all.
Just one opinion.
FWIW, I bind `M-%' to a command that rolls together these q-r
behaviors:
* No prefix arg: string q-r (like vanilla `query-replace')
* Negative prefix arg: regexp q-r
* Non-negative prefix arg: word q-r (like vanilla `query-replace')
next prev parent reply other threads:[~2013-08-03 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:10 bug#14979: 24.3; Feature Request: query-replace-backward Ben A.
2013-07-29 7:12 ` Jambunathan K
2013-07-29 7:16 ` Jambunathan K
2013-07-29 8:22 ` Juri Linkov
2013-07-29 8:47 ` Jambunathan K
2013-07-29 21:02 ` Juri Linkov
2013-07-30 20:09 ` ben.a
2013-08-01 21:13 ` Juri Linkov
2013-08-03 20:44 ` Ben A.
2013-08-03 21:24 ` Drew Adams [this message]
2013-12-17 19:35 ` Juri Linkov
2013-12-19 0:30 ` Juri Linkov
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=5819bbc4-bf73-47a3-92e5-e4f7fde0cf55@default \
--to=drew.adams@oracle.com \
--cc=14979@debbugs.gnu.org \
--cc=ben.a@gmx.us \
--cc=juri@jurta.org \
--cc=kjambunathan@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).