unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Allen Li <vianchielfaura@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 28008@debbugs.gnu.org
Subject: bug#28008: 25.2; Resume kmacro definition errors C-u C-u <F3>
Date: Fri, 29 Sep 2017 20:47:54 -0700	[thread overview]
Message-ID: <CAJr1M6eEEOceknB5fPSbYWy7JDb=nbT0Eaz5jvpO9aZG+Qgkbg@mail.gmail.com> (raw)
In-Reply-To: <CAJr1M6fTpMvFW0==YGstHPakjjbPwEm9cGhtQ0RLdw8XUvq++A@mail.gmail.com>

On Tue, Sep 19, 2017 at 12:42 AM, Allen Li <vianchielfaura@gmail.com> wrote:
> 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.
> ---
>  lisp/subr.el | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/lisp/subr.el b/lisp/subr.el
> index 79ae1f4830..f0c4e2969d 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -785,8 +785,9 @@ undefined
>    "Beep to tell the user this binding is undefined."
>    (interactive)
>    (ding)
> -  (message "%s is undefined" (key-description (this-single-command-keys)))
> -  (setq defining-kbd-macro nil)
> +  (if defining-kbd-macro
> +      (error "%s is undefined" (key-description (this-single-command-keys)))
> +    (message "%s is undefined" (key-description (this-single-command-keys))))
>    (force-mode-line-update)
>    ;; If this is a down-mouse event, don't reset prefix-arg;
>    ;; pass it to the command run by the up event.
> --
> 2.14.1

Any updates on this? I have been running this patch locally (monkey
patched) for a week without any issues.





  reply	other threads:[~2017-09-30  3:47 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 [this message]
2017-09-30  4:20     ` Tino Calancha
2017-09-30 13:48   ` Eli Zaretskii
2020-08-24 14:07     ` Lars Ingebrigtsen
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

  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='CAJr1M6eEEOceknB5fPSbYWy7JDb=nbT0Eaz5jvpO9aZG+Qgkbg@mail.gmail.com' \
    --to=vianchielfaura@gmail.com \
    --cc=28008@debbugs.gnu.org \
    --cc=tino.calancha@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 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).