From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Spencer Baugh <sbaugh@janestreet.com>, 67836@debbugs.gnu.org
Subject: bug#67836: 29.1.90; map-y-or-n-p doesn't terminate when run in a kmacro in batch mode
Date: Fri, 15 Dec 2023 17:55:43 -0500 [thread overview]
Message-ID: <jwv1qbn5bfj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83msubo2vw.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 15 Dec 2023 18:18:43 +0200")
> Thanks, but let's please find a fix that doesn't make the tail wag the
> dog. I don't want to make a change in bitch_at_user, which will
> affect every possible use of it in batch mode, something that we have
> been doing for eons.
I suspect keyboard macros have not been used very much in batch mode
over the last 32 years.
>> ding's docstring states that it terminates keyboard macros. But, due
>> to what seems to be an oversight, it does not do that while executing
>> in batch mode.
> As the code clearly shows, it isn't an oversight.
AFAICT the current logic of code can be traced back to:
commit 4588ec205730239596486e8ad4d18d541917199a
Author: Jim Blandy <jimb@red-bean.com>
Date: Wed Jul 3 12:10:07 1991 +0000
Initial revision
diff --git a/src/dispnew.c b/src/dispnew.c
--- /dev/null
+++ b/src/dispnew.c
@@ -0,0 +1813,9 @@
+{
+ if (noninteractive)
+ putchar (07);
+ else if (!INTERACTIVE) /* Stop executing a keyboard macro. */
+ error ("Keyboard macro terminated by a command ringing the bell");
+ else
+ ring_bell ();
+ fflush (stdout);
+}
I'm not sure this code can be said to show clearly that it's not
an oversight.
I read it to say that the author did not consider the intersection of
noninteractive
and
!INTERACTIVE
-- Stefan
next prev parent reply other threads:[~2023-12-15 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 15:38 bug#67836: 29.1.90; map-y-or-n-p doesn't terminate when run in a kmacro in batch mode Spencer Baugh
2023-12-15 15:44 ` Spencer Baugh
2023-12-15 16:18 ` Eli Zaretskii
2023-12-15 22:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-16 8:11 ` Eli Zaretskii
2023-12-16 13:13 ` sbaugh
2023-12-16 13:52 ` Eli Zaretskii
2023-12-16 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 15:55 ` Eli Zaretskii
2023-12-16 16:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 17:24 ` Eli Zaretskii
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=jwv1qbn5bfj.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=67836@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.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).