unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
	Tino Calancha <tino.calancha@gmail.com>,
	24977@debbugs.gnu.org
Subject: bug#24977: 25.1; search and query-replace in Dired
Date: Mon, 21 Nov 2016 13:10:55 -0800 (PST)	[thread overview]
Message-ID: <a76a432e-8b7a-4ff0-a52b-816c5f785231@default> (raw)
In-Reply-To: <dde37229-390a-5368-dd05-6a0a08c889a0@yandex.ru>

> > I have no argument with the new commands.  My argument is to keep
> > the old commands as well, with their bindings and menu items, and
> > to give the new commands new bindings and new menu items.
> 
> Because that wouldn't be confusing. Either the menu items will look
> almost the same (but perform slightly differently), or they will
> have to be very long, to describe the difference.

They _should_ be similar because the functionality is similar
(regexp search & query-replace).  Their difference should reflect
their main difference.  The main difference I see is that one
searches using (any) Emacs regexps and the other searches using
`find' (with all of its advantages and disadvantages).

"... Using `find'" or "... With `find'" in the new menu items is
not long, and it says quite a _lot_ about what the command does.

> > When you kinda sorta sometimes
> > get behavior that is similar to what you might expect (e.g. from
> > the regexp alone), the actual behavior can be all the more
> > confusing if this difference is not described clearly.
> 
> Indeed. But careful handling of uncertain cases and showing user-
> error for tricky regexps should make the behavior make sense.

Making some more sense is no doubt possible.  Handling some
more cases is no doubt possible.  But as you said, some things
are not possible ("We obviously can't support those"), and any
simulation of ordinary Emacs searching would be ad hoc.

Again, I have no problem with adding these useful commands.
The problem is subtracting the older, also useful commands
(and their key bindings).  There is no reason to do that.





  reply	other threads:[~2016-11-21 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-11-21 16:24 ` Eli Zaretskii
     [not found] <<d27abfa8-adc7-4e5f-ab6e-c1b0824e50a0@default>
     [not found] ` <<83h97094yh.fsf@gnu.org>
2016-11-21 16:36   ` Drew Adams

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=a76a432e-8b7a-4ff0-a52b-816c5f785231@default \
    --to=drew.adams@oracle.com \
    --cc=24977@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=tino.calancha@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).