From: Lars Ingebrigtsen <larsi@gnus.org>
To: charles@aurox.ch (Charles A. Roelli)
Cc: tim.nielens@gmail.com, 18611@debbugs.gnu.org
Subject: bug#18611: 24.3; macre step edit and use of registers
Date: Wed, 14 Jul 2021 00:08:22 +0200 [thread overview]
Message-ID: <87zgupn9yh.fsf@gnus.org> (raw)
In-Reply-To: <m28tg2b295.fsf@aurox.ch> (Charles A. Roelli's message of "Mon, 23 Oct 2017 12:13:42 +0200")
charles@aurox.ch (Charles A. Roelli) writes:
>> Something similar still affects emacs-26. Thanks for the report.
>>
>> To reproduce from emacs -q:
>> C-x b RET
>> C-x h
>> C-x r s i
>> M->
>> F3
>> C-x r i i
>> F4
>> C-x C-k SPC
>> y
>> Error in post-command-hook (kmacro-step-edit-post-command):
>> (void-variable kmacro-step-edit-active)
>> C-x C-k SPC
>> (observe that the last "i" in "C-x r i i" is gone)
>>
>> Actually, the following is enough to trigger the error from emacs -q:
>> C-x b RET
>> C-x C-k SPC
>> (i.e., when the last kbd macro doesn't exist)
>
> As of the fix for Bug#28818, the (void-variable
> kmacro-step-edit-active) errors should be gone, but the buggy register
> behavior remains.
(I'm going through old bug reports that unfortunately got little
response at the time.)
As noted, the void-variable error is gone, but I'm not sure what the
buggy register behaviour here is? I tried the recipe, and it seemed to
work fine? That is `C-x C-k SPC y' executed the register insertion
command fine, as far as I can tell.
So are you still seeing this issue, or did I just misunderstand what the
problem here is?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-13 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 7:45 bug#18611: 24.3; macre step edit and use of registers Tim Nielens
2017-09-21 19:01 ` Charles A. Roelli
2017-10-23 10:13 ` Charles A. Roelli
2021-07-13 22:08 ` Lars Ingebrigtsen [this message]
2021-08-11 20:41 ` Lars Ingebrigtsen
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=87zgupn9yh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18611@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=tim.nielens@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).