From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: ARG and Dired commands, was: Re: [External] : Re: master 2ed2999: Improve documentation of new Xref options
Date: Tue, 7 Sep 2021 20:42:03 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884E376F6897DFE09E63B0F3D39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <0a6bfe4f-f6b4-79eb-dd82-2cea53430ab4@yandex.ru>
> > I was talking about the behavior of the ARG argument.
> > And I think I'm correct about that: they accept and
> > handle ARG the same way.
>
> Then we're really having different discussions. May I ask you to read
> the contents of the thread next time before replying?
May I ask you not to add `dired-do-*' commands that
are inconsistent with the existing ones regarding ARG?
(I do care about vanilla Emacs, even if I can fix such
blunders in Dired+.)
> > But mea culpa. You found one exception (out of 26
> > such commands in vanilla Emacs): with `emacs -Q',
> > `dired-do-search' does not accept an ARG argument:
> >
> > It_should_ accept an optional ARG, IMO. Would you
> > like to fix that minor bug?;-)
>
> Considering that neither dired-do-search nor
> dired-do-query-replace-regexp have an ARG argument,
Bravo! You found a second one. So 2 out of 26.
> it doesn't seem logical for the newer counterparts
> to have it.
It does to me. Why doesn't it to you?
A user will expect the same ARG behavior with a
prefix arg, IMO. Why wouldn't s?he? The principle
of least surprise, Occam's razor, and common sense
argue in favor.
Sure, it's possible to have exceptions, IF there's
a good reason (and unfamiliarity with Dired isn't
a good reason). Do you really have a good reason?
I offered you a simple way out: add your own
command with its own name - just don't prefix it
with `dired-do-'.
> Either way, it's orthogonal to the question at hand.
It's not orthogonal if you're adding a command
named `dired-do-*' that doesn't accept a prefix-arg
ARG with the usual behavior.
You were able to find 2 exceptions out of 26 commands.
That's NOT a good reason to add a 3rd exception.
Maybe you have a reason that's good, but that one ain't.
next prev parent reply other threads:[~2021-09-07 20:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210905075953.20536.20920@vcs0.savannah.gnu.org>
[not found] ` <20210905075955.0F6B720A0A@vcs0.savannah.gnu.org>
2021-09-05 19:38 ` master 2ed2999: Improve documentation of new Xref options Dmitry Gutov
2021-09-06 4:30 ` Eli Zaretskii
2021-09-06 11:24 ` Dmitry Gutov
2021-09-06 12:28 ` Eli Zaretskii
2021-09-06 12:47 ` Dmitry Gutov
2021-09-06 15:33 ` Eli Zaretskii
2021-09-06 15:43 ` Dmitry Gutov
2021-09-07 13:05 ` Eli Zaretskii
2021-09-07 15:24 ` Dmitry Gutov
2021-09-07 15:27 ` Dmitry Gutov
2021-09-07 16:07 ` Eli Zaretskii
2021-09-07 15:47 ` Eli Zaretskii
2021-09-07 16:01 ` Dmitry Gutov
2021-09-07 16:18 ` Eli Zaretskii
2021-09-07 16:27 ` Dmitry Gutov
2021-09-07 17:03 ` [External] : " Drew Adams
2021-09-07 17:21 ` Dmitry Gutov
2021-09-07 17:28 ` Drew Adams
2021-09-07 17:40 ` Dmitry Gutov
2021-09-07 19:44 ` Drew Adams
2021-09-07 20:08 ` ARG and Dired commands, was: " Dmitry Gutov
2021-09-07 20:42 ` Drew Adams [this message]
2021-09-07 20:49 ` Dmitry Gutov
2021-09-07 21:47 ` 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=SJ0PR10MB54884E376F6897DFE09E63B0F3D39@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).