From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: vianchielfaura@gmail.com, 28008@debbugs.gnu.org
Subject: bug#28008: 25.2; Resume kmacro definition errors C-u C-u <F3>
Date: Fri, 11 Aug 2017 16:00:56 +0300 [thread overview]
Message-ID: <83shgyqmwn.fsf@gnu.org> (raw)
In-Reply-To: <87d182p97t.fsf@calancha-pc> (message from Tino Calancha on Fri, 11 Aug 2017 21:41:58 +0900)
> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 28008@debbugs.gnu.org, tino.calancha@gmail.com
> Date: Fri, 11 Aug 2017 21:41:58 +0900
>
> ** Patch 1 always save the macro in `last-kbd-macro' after an error or 'C-g'.
> Then, A. B. and D.2 behaves similarly.
>
> ** Patch 2 adds a new variable `last-aborted-kbd-macro': it saves the partial
> macro there after an error or 'C-g'. Called `start-kbd-macro' with
> APPEND non-nil offers to append on `last-aborted-kbd-macro'; possible answers
> are 'yes', 'no' or 'del' (i.e., append on `last-aborted-kbd-macro' after delete
> its last character).
>
> This is not backward compatible; for instance, the snippets A, B above won't be
> saved in `last-kbd-macro' (currently they do).
> It's more tidy; it separates 'good macros', i.e. those ended after
> 'F4' or 'C-x )', from 'partial macros', i.e., those ended after an error or 'C-g'.
All these low-level changes just to support an obscure use case? Is
really worth the risk to break macros to cater to that?
Thanks.
next prev parent reply other threads:[~2017-08-11 13:00 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 [this message]
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
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=83shgyqmwn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28008@debbugs.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.