[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "
From: |
Drew Adams |
Subject: |
bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters |
Date: |
Wed, 8 May 2019 15:39:56 -0700 (PDT) |
> Drew Adams <drew.adams@oracle.com> writes:
>
> > I don't see any good reason why face `minibuffer-prompt'
> > should be used, especially by default (users can do
> > whatever they like) for situations where there is no
> > active minibuffer, i.e., for prompting situations
> > generally. It should instead serve as a useful clue
> > that the minibuffer is being used. (Just one opinion.)
>
> I'd hazard a guess[1] that this was done to make y-or-n-p and
> yes-or-no-p similar from a UI point of view: they both prompt the user
> for a binary answer, therefore the prompt might as well look the same in
> both situations.
>
> From what I can tell the use of 'minibuffer-prompt' in minibuffer-less
> situations has enough precedents (the "other clients" Martin mentions)
> that the "minibuffer-" prefix might be considered a historical accident
> by now…
Not an accident. The "precedents" are themselves bugs,
IMO. The minibuffer is the minibuffer. It's important
that users be aware when it is active. That may not
matter much for `yes-or-no-p', as it insists on "yes"
or "no". But it is important for the minibuffer in
general. The minibuffer is an editing buffer; you can
do lots of things in it and with it.
> (Perhaps those clients could be migrated to a new face,
> e.g. 'message-prompt', which would inherit 'minibuffer-prompt' by
> default?)
That would be fine by me. Or no face. Is it really
important that the prompt be distinguished by a face?
(To be clear, I have no objection to our using faces
for prompts.)
> - In the context of bug#35564, I would like to add text properties to
> the y-or-n-p prompt (although I'm open to other, simpler solutions
> e.g. simply changing Dired's message).
I wouldn't mention bug #35564. And that bug should not,
itself, also deal with prompt faces. It should be only
about `dired-do-shell-command' warning about wildcard
characters.
Any question (for this command or in general) about
prompt faces is independent of this bug report about
the `dired-do-shell-command' treatment of wildcards.
(Just one opinion.)
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Kévin Le Gouguec, 2019/05/04
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, martin rudalics, 2019/05/05
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Kévin Le Gouguec, 2019/05/06
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, martin rudalics, 2019/05/07
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Drew Adams, 2019/05/07
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Kévin Le Gouguec, 2019/05/08
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters,
Drew Adams <=
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, martin rudalics, 2019/05/09
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Drew Adams, 2019/05/09
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, martin rudalics, 2019/05/09
- bug#35564: 27.0.50; [PATCH] Tweak dired-do-shell-command warning about "wildcard" characters, Drew Adams, 2019/05/09