GNU bug report logs -
#40653
28.0.50; (fset 'yes-or-no-p 'y-or-n-p) has no effect in native-comp branch
Previous Next
Reported by: Andrey Orst <andreyorst <at> gmail.com>
Date: Thu, 16 Apr 2020 08:00:02 UTC
Severity: normal
Found in version 28.0.50
Done: Andrea Corallo <akrl <at> sdf.org>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 40653 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On master branch the `fset` command does what expected - prompts that ask
for `yes` or `no` changed to ask `y` or `n`. On native-comp branch however
it has no effect and all prompts still ask for `yes` or `no` after `fset`
call.
On Thu, Apr 16, 2020 at 11:18 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Andrey Orst <andreyorst <at> gmail.com>
> > Date: Thu, 16 Apr 2020 10:59:12 +0300
> >
> > Call `emacs -q` do `M-x ansi-term RET` try to kill buffer - a prompt
> > with `yes` or `no` will be provided. Cancel and call `M-: (fset
> > 'yes-or-no-p 'y-or-n-p) RET`, and try to kill ansi-term buffer
> > again. Prompt will still ask to input `yes` or `no` instead of `y` or
> > `n`. Works in master branch of Emacs run with `-q`.
>
> I'm not sure I understand the issue. The last sentence seems to say
> this works as expected on the master branch? That is, the prompt does
> ask to input 'y' or 'n', right? Because that's what I see with
> today's master.
>
--
Best regards,
Andrey Orst
[Message part 2 (text/html, inline)]
This bug report was last modified 5 years and 76 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.