From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 62126@debbugs.gnu.org
Subject: bug#62126: 26.3; Doc of `dired-do(-async)-shell-command': mention `dired-guess-shell-command'
Date: Sun, 12 Mar 2023 17:27:01 +0200 [thread overview]
Message-ID: <83ttyqt2gq.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488559BBABEE2EECC535325F3B89@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 12 Mar 2023 15:07:44 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "62126@debbugs.gnu.org" <62126@debbugs.gnu.org>
> Date: Sun, 12 Mar 2023 15:07:44 +0000
>
> > > > It would help if the doc of these commands (and others that use
> > > > `dired-read-shell-command') mentioned that if `dired-x' is loaded then
> > > > they make use of option `dired-guess-shell-command' to guess an
> > > > appropriate default value (command).
> > >
> > > It already does, in Emacs 27 and later.
>
> Thanks; I missed that.
>
> > Actually, I see that in Emacs 26.3 as well, so I'm not sure why you
> > didn't. Maybe you didn't mention all the commands you had in mind?
>
> Where do you see it in 26.3? I didn't find it there.
> I don't see it there in either of those doc strings.
> I don't see it in the Emacs manual, where those
> commands are doc'd (or anywhere else). I don't see
> it in the Elisp manual. But I haven't had any coffee
> yet this morning...
Maybe this is a misunderstanding. How about if you show the doc
strings of the offending functions and tell explicitly what is missing
from them?
next prev parent reply other threads:[~2023-03-12 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:58 bug#62126: 26.3; Doc of `dired-do(-async)-shell-command': mention `dired-guess-shell-command' Drew Adams
2023-03-12 8:42 ` Eli Zaretskii
2023-03-12 9:16 ` Eli Zaretskii
2023-03-12 15:07 ` Drew Adams
2023-03-12 15:27 ` Eli Zaretskii [this message]
2023-03-12 15:59 ` Drew Adams
2023-03-12 20:13 ` Eli Zaretskii
2023-03-12 22:13 ` 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=83ttyqt2gq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62126@debbugs.gnu.org \
--cc=drew.adams@oracle.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).