From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: master 2ed2999: Improve documentation of new Xref options
Date: Tue, 7 Sep 2021 20:21:32 +0300 [thread overview]
Message-ID: <74b49161-c552-19d3-7111-b75cb551c1c7@yandex.ru> (raw)
In-Reply-To: <SJ0PR10MB548829B9790764E9B30D0D19F3D39@SJ0PR10MB5488.namprd10.prod.outlook.com>
On 07.09.2021 20:03, Drew Adams wrote:
> If possible, `dired-do-*' commands should
> behave similarly. There's value in them
> having a consistent interface.
>
> So much so that I'd say that if some command
> has to break this consistency then its name
> shouldn't use the prefix `dired-do-'. Just
> one opinion, of course.
find-tag and find-file also have a matching first word in the name.
next prev parent reply other threads:[~2021-09-07 17:21 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74b49161-c552-19d3-7111-b75cb551c1c7@yandex.ru \
--to=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--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 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.