From: Andrey Orst <andreyorst@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40653@debbugs.gnu.org
Subject: bug#40653: 28.0.50; (fset 'yes-or-no-p 'y-or-n-p) has no effect in native-comp branch
Date: Thu, 16 Apr 2020 11:21:19 +0300 [thread overview]
Message-ID: <CAAKhXoYF1EA-tvPN7D_AJ4mM5eJED-PfSgym9GPg0kYVh5hrOg@mail.gmail.com> (raw)
In-Reply-To: <83v9lzetdp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
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@gnu.org> wrote:
> > From: Andrey Orst <andreyorst@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
[-- Attachment #2: Type: text/html, Size: 1624 bytes --]
next prev parent reply other threads:[~2020-04-16 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 7:59 bug#40653: 28.0.50; (fset 'yes-or-no-p 'y-or-n-p) has no effect in native-comp branch Andrey Orst
2020-04-16 8:18 ` Eli Zaretskii
2020-04-16 8:21 ` Andrey Orst [this message]
2020-04-16 8:51 ` Eli Zaretskii
2020-04-16 9:01 ` Andrea Corallo
2020-04-16 9:58 ` Andrey Orst
2020-04-16 16:49 ` Andrea Corallo
2020-04-16 22:14 ` Sebastian Sturm
2020-04-17 11:26 ` Andrea Corallo
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=CAAKhXoYF1EA-tvPN7D_AJ4mM5eJED-PfSgym9GPg0kYVh5hrOg@mail.gmail.com \
--to=andreyorst@gmail.com \
--cc=40653@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).