From: Stefan Kangas <stefan@marxist.se>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 18864-done@debbugs.gnu.org, Andreas Ehliar <ehliar@isy.liu.se>
Subject: bug#18864: 24.4; F4 may be inserted into emacs macro when blink-matching-paren is enabled
Date: Mon, 30 Sep 2019 03:49:39 +0200 [thread overview]
Message-ID: <CADwFkmmi4fcmTDV4iydM5wqgjznSR_yCgdxKAbUYB=TLxjMwSA@mail.gmail.com> (raw)
In-Reply-To: <8e3ca424887ffdad481a997720e92f8c@isy.liu.se>
Marcin Borkowski <mbork@mbork.pl> writes:
> On 2014-10-27, at 11:28, Andreas Ehliar <ehliar@isy.liu.se> wrote:
>
>> Starting from emacs -Q:
>> * Open an html file (e.g. /tmp/foo.html)
>> * Type <b
>> * Start a macro with F3
>> * Quickly enter > followed by F4
>> * M-x edit-last-kbd-macro now shows that F4 has been inserted into the
>> macro.
>>
>> I believe that this bug is, in some way, caused by
>> blink-matching-paren.
>> F4 only seems to be entered into the macro when the preceding "<" is
>> highlighted.
>>
>> Also, I cannot reproduce the bug when setting blink-matching-paren to
>> nil.
>>
>> I originally saw this problem in 24.3, but I have just compiled 24.4
>> to confirm that the bug is still present there.
>
> Hello,
>
> I have just tried to reproduce it on GNU Emacs 25.1.50.4 (commit
> f182640), and could not. Could you confirm that this is no longer
> a problem? (If you do not want to compile Emacs from the Git repo,
> maybe try the latest pretest, see
> http://alpha.gnu.org/gnu/emacs/pretest/)
More information was requested, but none was given within close to 4
years, so I'm closing this bug report. If this is still an issue,
please reopen the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-09-30 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:28 bug#18864: 24.4; F4 may be inserted into emacs macro when blink-matching-paren is enabled Andreas Ehliar
2016-03-01 16:11 ` Marcin Borkowski
2019-09-30 1:49 ` Stefan Kangas [this message]
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='CADwFkmmi4fcmTDV4iydM5wqgjznSR_yCgdxKAbUYB=TLxjMwSA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=18864-done@debbugs.gnu.org \
--cc=ehliar@isy.liu.se \
--cc=mbork@mbork.pl \
/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.