From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 28525@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#28525: 26.0.60; dired-delete-file: Accept y/n if yes-or-no-p is aliased to y-or-n-p
Date: Mon, 02 Oct 2017 20:41:15 +0300 [thread overview]
Message-ID: <83wp4d1m84.fsf@gnu.org> (raw)
In-Reply-To: <87poa7tstz.fsf@gmail.com> (message from Tino Calancha on Sun, 01 Oct 2017 13:06:32 +0900)
> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: 28525@debbugs.gnu.org, npostavs@users.sourceforge.net
> Date: Sun, 01 Oct 2017 13:06:32 +0900
>
> Tino Calancha <tino.calancha@gmail.com> writes:
>
> > In my previous patch i checked if `yes-or-no-p' is aliased to
> > `y-or-n-p'.
> > A more general way is to add new functions `yes-or-no-or-else-p',
> > `y-or-n-or-else-p': they ask the question and
> > accept additional answers according with an optional argument.
> Indeed, we don't need new functions just add an optional argument makes
> the thing (see below patch).
> In some cases it might be useful to allow more answers than just 'yes'
> or 'no'.
On second thought, maybe we should simply ignore this issue, and let
users who want to override these functions write their own variants
for them? Especially since packages do exist out there to do
something like that already. We don't need to solve every single
problem with exotic customizations in the core.
WDYT?
next prev parent reply other threads:[~2017-10-02 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 9:51 bug#28525: 26.0.60; dired-delete-file: Accept y/n if yes-or-no-p is aliased to y-or-n-p Tino Calancha
2017-09-21 8:15 ` Eli Zaretskii
2017-09-30 13:00 ` Tino Calancha
2017-10-01 4:06 ` Tino Calancha
2017-10-01 23:15 ` Drew Adams
2017-10-02 5:40 ` Tino Calancha
2017-10-02 13:33 ` Drew Adams
2017-10-03 8:02 ` Tino Calancha
2017-10-02 17:41 ` Eli Zaretskii [this message]
2017-10-03 8:00 ` Tino Calancha
2017-10-03 11:10 ` Michael Heerdegen
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=83wp4d1m84.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28525@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--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).