From: Drew Adams <drew.adams@oracle.com>
To: Allen Li <vianchielfaura@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 29465@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#29465: 25.3; Confusing message for dired-do-shell-command substitution
Date: Tue, 28 Nov 2017 20:20:38 -0800 (PST) [thread overview]
Message-ID: <29b407d1-e1f6-4676-a686-ccdf19af8bb4@default> (raw)
In-Reply-To: <CAJr1M6cT578dcFT4Uvg29===-q=7omx5DG+JSTuqczjO3paGgg@mail.gmail.com>
I have not been following this thread, so apologies if
this doesn't help or isn't very relevant.
IF we feel it helps a user to prompt about something,
and IF we feel there is a possibility that some users
might not understand the prompt, in spite of our best
efforts to come up with a good prompt, and IF we feel
that understanding the prompt is important, THEN the
doc string should make clear whatever it is that it
is important that users understand about that prompting.
It's quite possible for a user not to understand even
a good prompt. S?he should be able to get the point
by doing `C-h f', in that case.
next prev parent reply other threads:[~2017-11-29 4:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 7:16 bug#29465: 25.3; Confusing message for dired-do-shell-command substitution Allen Li
2017-11-27 7:34 ` Allen Li
2017-11-27 9:07 ` Michael Heerdegen
2017-11-27 15:58 ` Eli Zaretskii
2017-11-28 3:50 ` Tino Calancha
2017-11-28 8:25 ` Allen Li
2017-11-28 16:26 ` Eli Zaretskii
2017-11-28 20:13 ` Allen Li
2017-11-29 4:20 ` Drew Adams [this message]
2017-12-01 8:36 ` Eli Zaretskii
2017-12-02 6:31 ` Allen Li
2017-12-02 7:32 ` Tino Calancha
2017-12-02 8:22 ` Allen Li
2022-03-22 16:48 ` Lars Ingebrigtsen
2017-11-28 16:15 ` Eli Zaretskii
[not found] <<CAJr1M6f71vv2W090wPw8q_10wK=OwfgvMfM7DMiPn9G8oyY8AA@mail.gmail.com>
[not found] ` <<83vahv67eb.fsf@gnu.org>
[not found] ` <<87fu8zukmb.fsf@gmail.com>
[not found] ` <<CAJr1M6cuB0RPcUfzsGHCGt+8m6-KH58FX4NoD==APb7dksrs2g@mail.gmail.com>
[not found] ` <<83609u5pyr.fsf@gnu.org>
[not found] ` <<CAJr1M6cT578dcFT4Uvg29===-q=7omx5DG+JSTuqczjO3paGgg@mail.gmail.com>
[not found] ` <<29b407d1-e1f6-4676-a686-ccdf19af8bb4@default>
[not found] ` <<83mv323kvx.fsf@gnu.org>
2017-12-01 15:42 ` 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=29b407d1-e1f6-4676-a686-ccdf19af8bb4@default \
--to=drew.adams@oracle.com \
--cc=29465@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
--cc=vianchielfaura@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).