From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: abela@chalmers.se, 31796@debbugs.gnu.org
Subject: bug#31796: 27.1; dired-do-find-regexp-and-replace fails to find multiline regexps
Date: Tue, 24 Nov 2020 13:35:40 -0800 (PST) [thread overview]
Message-ID: <142b3234-a15a-4850-8eea-4bbe89de7169@default> (raw)
In-Reply-To: <<831rgitqe2.fsf@gnu.org>>
> > >> dired-do-find-regexp-and-replace could be left bound to Q, but
> > >> dired-do-query-replace-regexp could be bound to M-% in Dired.
> > >
> > > How will this help when the command to continue the loop is not
> > > bound to any key?
> >
> > dired-do-query-replace-regexp works like normal 'M-%' with 'y/n/!'
> > keys and automatically moves to the next file on multiple files.
> > So it seemes it doesn't need a key to continue the loop.
>
> AFAIR, it does need a way to continue the loop if the user exits the
> loop.
If that feature is needed and broken, then that's true
for the command itself (`dired-do-query-replace-regexp'),
right?
It has nothing to do with whether or not that command
has a key binding, and even less to do with whether it
has the key binding `Q'. No?
I guess you're (not saying but hinting?) that the
decision to take key `Q' away from that command also
took away the ability to continue the loop if the user
exits it. If so, that too is (apparently) unfortunate.
But what does that have to do with giving that command a
key binding (e.g. `M-q')?
What am I missing?
next prev parent reply other threads:[~2020-11-24 21:35 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<CADy8Bt=f=LOE6ODLhhW7ZS6qXRQCzd15Hd0eFKVO8qok98ni8w@mail.gmail.com>
[not found] ` <<10120030-8b8d-b702-add4-8f099f934ed5@chalmers.se>
[not found] ` <<91c98791-9df2-43ee-9aac-205c5b0de9c2@default>
[not found] ` <<87blfm6922.fsf@mail.linkov.net>
[not found] ` <<838saqtsm9.fsf@gnu.org>
2020-11-24 20:32 ` bug#31796: 27.1; dired-do-find-regexp-and-replace fails to find multiline regexps Drew Adams
[not found] ` <<87mtz64htw.fsf@mail.linkov.net>
[not found] ` <<831rgitqe2.fsf@gnu.org>
2020-11-24 21:35 ` Drew Adams [this message]
2018-06-11 18:58 bug#31796: 26.1; " Žygimantas Bruzgys
2018-06-12 10:17 ` Noam Postavsky
2020-11-23 21:25 ` Dmitry Gutov
2020-11-23 9:09 ` bug#31796: 27.1; " Andreas Abel
2020-11-23 15:23 ` Eli Zaretskii
2020-11-23 16:16 ` Drew Adams
2020-11-23 21:22 ` Dmitry Gutov
2020-11-24 19:28 ` Juri Linkov
2020-11-24 20:12 ` Drew Adams
2020-11-25 7:31 ` Juri Linkov
2020-11-25 17:37 ` Drew Adams
2020-11-24 20:19 ` Eli Zaretskii
2020-11-24 20:31 ` Juri Linkov
2020-11-24 20:51 ` Drew Adams
2020-11-24 21:07 ` Eli Zaretskii
2020-11-25 7:28 ` Juri Linkov
2020-11-25 15:48 ` Eli Zaretskii
2020-11-25 20:18 ` Juri Linkov
2020-11-25 20:30 ` Eli Zaretskii
2020-11-29 2:30 ` Dmitry Gutov
2020-11-29 15:22 ` Eli Zaretskii
2020-11-23 21:28 ` Dmitry Gutov
2020-11-23 23:49 ` Andreas Abel
2020-11-24 0:13 ` Dmitry Gutov
2020-11-24 1:19 ` Dmitry Gutov
2020-11-24 15:16 ` Eli Zaretskii
2020-11-24 15:43 ` Dmitry Gutov
2020-11-24 16:35 ` Eli Zaretskii
2020-11-24 19:43 ` Dmitry Gutov
2020-11-24 20:16 ` Eli Zaretskii
2020-11-30 2:25 ` Dmitry Gutov
2020-11-30 8:49 ` Juri Linkov
2020-12-01 2:21 ` Dmitry Gutov
2020-12-01 8:39 ` Juri Linkov
2020-12-03 2:46 ` Dmitry Gutov
2020-12-06 21:00 ` Juri Linkov
2020-12-16 3:00 ` Dmitry Gutov
2020-12-16 20:32 ` Juri Linkov
2020-12-17 0:40 ` Dmitry Gutov
2020-11-30 15:30 ` Eli Zaretskii
2020-11-30 15:39 ` Jean Louis
2020-11-30 16:36 ` Eli Zaretskii
2020-11-30 15:42 ` Jean Louis
2020-12-01 1:23 ` Dmitry Gutov
2020-12-01 8:36 ` Juri Linkov
2020-12-01 15:20 ` Dmitry Gutov
2020-12-01 1:24 ` Dmitry Gutov
2020-12-01 5:20 ` Richard Stallman
2020-12-01 15:46 ` Eli Zaretskii
2020-12-02 4:26 ` Richard Stallman
2020-12-02 14:56 ` Eli Zaretskii
2020-12-02 17:17 ` Dmitry Gutov
2020-12-02 17:39 ` Eli Zaretskii
2020-12-02 17:43 ` Dmitry Gutov
2020-12-02 17:47 ` Eli Zaretskii
2020-12-03 5:26 ` Richard Stallman
2020-12-03 2:23 ` Dmitry Gutov
2020-11-24 19:29 ` Juri Linkov
2020-11-24 19:39 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=142b3234-a15a-4850-8eea-4bbe89de7169@default \
--to=drew.adams@oracle.com \
--cc=31796@debbugs.gnu.org \
--cc=abela@chalmers.se \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.