From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: contovob@tcd.ie, 30073@debbugs.gnu.org,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#30073: 27.0.50; dired-do-delete ignores customization for short answers
Date: Tue, 16 Jan 2018 01:13:04 +0200 [thread overview]
Message-ID: <87d12aaedz.fsf@mail.linkov.net> (raw)
In-Reply-To: <e68e905a-6eca-4a79-8027-60d9f251f41b@default> (Drew Adams's message of "Mon, 15 Jan 2018 09:01:24 -0800 (PST)")
> Do we all agree on the following points?
>
> 1. Users advising the yes/no confirmation-prompt functions
> is not a good solution to users wanting to sometimes (or
> always) use a different prompting approach from the one
> chosen by the author of the code that prompts.
I agree that advising the yes/no confirmation is not good
from a customization standpoint.
> 2. Choosing a single prompt approach (e.g. `y-or-n-p' or
> `yes-or-no-p') for all contexts might be appropriate for
> some users, but it is probably not a great idea in general.
Please see an optional argument ‘short’ that I added to my previous
patch. It will allow using short answers even when customizable
variable is nil where code authors deem appropriate.
> 3. Even a given user might appreciate that a given prompting
> context asks them using the slow approach (`yes-or-no-p')
> at first, or most of the time, but she might sometimes,
> or even generally after some experience, prefer that that
> prompting context use a faster approach (e.g. `y-or-n-p').
I'm not sure if we need more fine-grained customization.
If the user decides that a short answer is enough, enough is enough.
next prev parent reply other threads:[~2018-01-15 23:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 21:41 bug#30073: 27.0.50; dired-do-delete ignores customization for short answers Juri Linkov
2018-01-11 3:00 ` Basil L. Contovounesios
2018-01-11 15:52 ` Eli Zaretskii
2018-01-11 17:34 ` Basil L. Contovounesios
2018-01-11 18:01 ` Eli Zaretskii
2018-01-11 19:39 ` Basil L. Contovounesios
2018-01-11 21:57 ` Juri Linkov
2018-01-11 21:54 ` Juri Linkov
2018-01-12 9:57 ` Eli Zaretskii
2018-01-13 22:38 ` Juri Linkov
2018-01-14 11:01 ` Tino Calancha
2018-01-14 22:53 ` Juri Linkov
2018-01-15 5:19 ` Eli Zaretskii
2018-01-15 23:02 ` Juri Linkov
2018-01-16 17:56 ` Eli Zaretskii
2018-01-17 22:56 ` Juri Linkov
2018-01-18 21:11 ` Juri Linkov
2018-01-15 17:01 ` Drew Adams
2018-01-15 23:13 ` Juri Linkov [this message]
2018-01-16 0:48 ` Drew Adams
2018-01-17 22:03 ` Juri Linkov
2018-01-18 3:36 ` Eli Zaretskii
2018-01-18 21:12 ` Juri Linkov
2018-01-21 21:46 ` Juri Linkov
2018-01-25 18:04 ` Drew Adams
2018-01-25 21:20 ` Juri Linkov
2018-01-25 21:48 ` Drew Adams
2018-01-26 7:57 ` Eli Zaretskii
2018-01-27 21:20 ` Juri Linkov
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=87d12aaedz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=30073@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=drew.adams@oracle.com \
--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.