From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 24977-done@debbugs.gnu.org
Subject: bug#24977: 25.1; search and query-replace in Dired
Date: Mon, 21 Nov 2016 08:36:55 -0800 (PST) [thread overview]
Message-ID: <845ed24d-8693-4691-aaaf-8f5b427a1563@default> (raw)
In-Reply-To: <<83h97094yh.fsf@gnu.org>>
> > However, you did NOT change the menu bindings for `dired-do-
> > search' and `dired-do-query-replace-regexp' (the commands formerly
> > bound to `A' and `Q'). This is inconsistent. Those menu items no
> > longer show the keyboard shortcuts, because they have none. And
> > the new commands are not on menus at all.
>
> Thanks, I fixed that now.
>
> > It was unwise to change the key bindings. They should be
> > restored, and new bindings should be sought for your new commands.
>
> Let's not start beating this dead horse again.
Then you did NOT fix this bug, and it should be closed as `wont fix'.
That's your choice, but please do not claim that you fixed the bug
that was reported if you did not.
The original search and query-replace commands, which were in the
menu, should also have keyboard key bindings (as before). AND the
new commands should be added to the menu.
For the menu, I suggest:
`Search Files' - as before
`Search Files using `find' - for the new command
`Query Replace' - as before
`Query Replace using `find' - for the new command
Logically, the longstanding key bindings `A' and `Q' should be
restored to the original commands. But if you refuse that then
they should at least be given other key bindings - `M-a' and
`M-q', for example.
Doing this, you can rightfully close this bug as fixed.
Otherwise, no.
next parent reply other threads:[~2016-11-21 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d27abfa8-adc7-4e5f-ab6e-c1b0824e50a0@default>
[not found] ` <<83h97094yh.fsf@gnu.org>
2016-11-21 16:36 ` Drew Adams [this message]
2016-11-21 1:54 bug#24977: 25.1; search and query-replace in Dired Drew Adams
2016-11-21 2:13 ` Drew Adams
2016-11-21 14:07 ` Tino Calancha
2016-11-21 16:47 ` Dmitry Gutov
2016-11-21 17:41 ` Drew Adams
2016-11-21 18:17 ` Dmitry Gutov
2016-11-21 18:37 ` Drew Adams
2016-11-21 18:42 ` Dmitry Gutov
2016-11-21 18:51 ` Drew Adams
2016-11-21 19:50 ` Dmitry Gutov
2016-11-21 21:10 ` Drew Adams
2016-11-21 16:24 ` Eli Zaretskii
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=845ed24d-8693-4691-aaaf-8f5b427a1563@default \
--to=drew.adams@oracle.com \
--cc=24977-done@debbugs.gnu.org \
--cc=eliz@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.
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).