From: npostavs@users.sourceforge.net
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 25665@debbugs.gnu.org, Chunyang Xu <mail@xuchunyang.me>
Subject: bug#25665: 26.0.50; [PATCH] Indicate prefix arg in minibuffer prompt for shell-command
Date: Thu, 09 Feb 2017 23:16:07 -0500 [thread overview]
Message-ID: <87a89un0jc.fsf@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1702101145001.2266@calancha-pc> (Tino Calancha's message of "Fri, 10 Feb 2017 12:05:29 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> writes:
> On Thu, 9 Feb 2017, npostavs@users.sourceforge.net wrote:
>
>> On Thu, Feb 9, 2017 at 11:53 AM, Tino Calancha <tino.calancha@gmail.com> wrote:
>>
>>> The meaning of the prefix argument must be explained in the docstring.
>>> That and the manual are the source of documentation, not the prompt.
>>
>> But it's nice if Emacs gives you a different prompt, so that you can be
>> sure you typed in the command correctly.
> Confirmation for having typed C-u?
> Well, sometimes some keys in old keyboards die... ;-)
We already have that in `echo-keystrokes'.
But I'm thinking also of times when you do C-u M-! and then switch to
another window to copy the command, then maybe when you come back, you
don't remember 100% what you were doing.
>> Just like M-& gives a
>> different prompt from M-!, even though you could figure out the
>> different meaning just by reading the docstring of each command.
> These are different commands so its Emacs (and whatever editor)
> convention to how a different prompt. The OP suggests to use
> a different prompt for the same command w/ or w/o prefix.
M-& and M-! are practically the same command anyway, async-shell-command
is basically just
(defun async-shell-command (command)
(shell-command (concat command "&")))
>
> There are lots of commands in Emacs accepting a raw,
> numeric prefix etc. If we change M-! prompt, we might
> also want to tune the prompt for all of them. Do we want that?
IMO yes, if the difference can be summarized in the prompt concisely
enough.
next prev parent reply other threads:[~2017-02-10 4:16 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
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 [this message]
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
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=87a89un0jc.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--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 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).