GNU bug report logs - #28525
26.0.60; dired-delete-file: Accept y/n if yes-or-no-p is aliased to y-or-n-p

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: npostavs <at> users.sourceforge.net, 28525 <at> debbugs.gnu.org
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

> From: Tino Calancha <tino.calancha <at> gmail.com>
> Cc: 28525 <at> debbugs.gnu.org,  npostavs <at> users.sourceforge.net
> Date: Sun, 01 Oct 2017 13:06:32 +0900
> 
> Tino Calancha <tino.calancha <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.