From: Drew Adams <drew.adams@oracle.com>
To: Tino Calancha <tino.calancha@gmail.com>,
Chunyang Xu <mail@xuchunyang.me>
Cc: 25665@debbugs.gnu.org
Subject: bug#25665: 26.0.50; [PATCH] Indicate prefix arg in minibuffer prompt for shell-command
Date: Thu, 9 Feb 2017 10:08:40 -0800 (PST) [thread overview]
Message-ID: <39fa3130-faca-49b8-a247-15f47f16504a@default> (raw)
In-Reply-To: <8760kjz4nv.fsf@calancha-pc>
> I am not sure about this.
> The meaning of the prefix argument must be explained in the docstring.
> That and the manual are the source of documentation, not the prompt.
>
> Having a short prompt is also good because there are more space
> in the line for the command; a short prompt is also better while tipying
> a long command: sometimes you want to change something at the beginning:
> < ; `beginning-of-buffer'
> Now you need to `C-f' several times to jump out of the prompt. The more
> verbose prompt, the more `C-f' you need.
>
> Just my opinion. Let's see what other people think.
+1
The minibuffer should simply echo that the prefix arg has been
used, and just what its numeric value is. It should not try
to explain what the possible values are and what they mean.
next prev parent reply other threads:[~2017-02-09 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 15:10 bug#25665: 26.0.50; [PATCH] Indicate prefix arg in minibuffer prompt for shell-command Chunyang Xu
2017-02-09 16:53 ` Tino Calancha
2017-02-09 18:08 ` Drew Adams [this message]
2017-02-09 20:31 ` Eli Zaretskii
2017-02-10 4:23 ` Chunyang Xu
2017-02-09 22:54 ` npostavs
2017-02-10 3:05 ` Tino Calancha
2017-02-10 4:16 ` npostavs
2017-02-10 7:13 ` Tino Calancha
2017-02-10 16:19 ` Noam Postavsky
2019-06-24 23:04 ` Lars Ingebrigtsen
[not found] <<m2wpczwgay.fsf@xuchunyang.me>
[not found] ` <<8760kjz4nv.fsf@calancha-pc>
[not found] ` <<83r3373y3f.fsf@gnu.org>
2017-02-09 21:00 ` 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=39fa3130-faca-49b8-a247-15f47f16504a@default \
--to=drew.adams@oracle.com \
--cc=25665@debbugs.gnu.org \
--cc=mail@xuchunyang.me \
--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 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.