From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Allen Li <vianchielfaura@gmail.com>,
28008@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#28008: 25.2; Resume kmacro definition errors C-u C-u <F3>
Date: Mon, 24 Aug 2020 16:07:29 +0200 [thread overview]
Message-ID: <878se4b0im.fsf@gnus.org> (raw)
In-Reply-To: <83bmls47qt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Sep 2017 16:48:58 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Actually, to fix case D.2 (where undefined keys exit kmacro definition
>> without saving), all that is needed is a short Emacs Lisp change.
>> This keeps the behavior of a bare C-g keyboard-abort of not saving the
>> kmacro.
>>
>> [PATCH] Make undefined keys exit and save kmacro definition
>>
>> * lisp/subr.el (undefined): Error out of kmacro definition.
>
> Thanks, pushed to the release branch.
Tino had a longer, more involved patch, but skimming this thread, it
seems like the patch that was applied handled the reported bug here?
I'm not quite sure, but I'm going to go ahead and close this bug report,
anyway. If there's anything more to be done here, please send a message
to the debbugs mail address, and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-24 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 4:10 bug#28008: 25.2; Resume kmacro definition errors C-u C-u <F3> Allen Li
2017-08-08 5:26 ` Tino Calancha
2017-08-08 17:16 ` Allen Li
2017-08-11 12:41 ` Tino Calancha
2017-08-11 13:00 ` Eli Zaretskii
2017-08-11 13:17 ` Tino Calancha
2017-08-12 3:03 ` Tino Calancha
2017-08-13 21:13 ` Allen Li
2017-09-18 20:02 ` Allen Li
2017-09-19 7:42 ` Allen Li
2017-09-30 3:47 ` Allen Li
2017-09-30 4:20 ` Tino Calancha
2017-09-30 13:48 ` Eli Zaretskii
2020-08-24 14:07 ` Lars Ingebrigtsen [this message]
2018-09-09 0:23 ` Allen Li
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878se4b0im.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=28008@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
--cc=vianchielfaura@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.