Re: yes-or-no-p prompt conditionally broken in master?

[Alan Mackenzie]

Hello, Eli.

On Fri, Sep 04, 2015 at 08:56:46PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 4 Sep 2015 13:34:39 +0000
> > Cc: Andreas Schwab <address@hidden>, address@hidden,
> >   address@hidden, address@hidden, address@hidden,
> >   address@hidden, address@hidden
> > From: Alan Mackenzie <address@hidden>

[ .... ]

> > If the defcustom has three values "Always-y-or-n", "Always-yes-or-no",
> > "depends-on-the-particular-invocation", I'm fine.  With just the first
> > two alternatives, I wouldn't like it.

> The intent is to provide a predicate defcustom that allows to cause
> yes-or-no-p behave like y-or-n-p.  y-or-n-p will always behave as it
> does, and I didn't intend to change that, as I don't see the use case
> for that.

> If you still want the 3rd alternative, please describe the use cases
> that would need it.

No, I don't.  I thought somebody else did.

There's been a fair amount of misunderstanding in this thread.  Sorry
for adding to it.

> > I'm wondering whether coalescing these two function is more trouble than
> > it's worth.

> Please don't worry about the implementation aspects.  It's not rocket
> science in any case.

OK.  Have a good weekend!

-- 
Alan Mackenzie (Nuremberg, Germany).