From: Tino Calancha <tino.calancha@gmail.com>
To: Marek Twardochlib <wasserwerk.studio@googlemail.com>
Cc: 25860@debbugs.gnu.org, eggert@cs.ucla.edu,
Noam Postavsky <npostavs@users.sourceforge.net>,
jwiegley@gmail.com, Tino Calancha <tino.calancha@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#25860: 25.1; Double macro execution
Date: Fri, 29 Sep 2017 20:41:48 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709292036310.26321@calancha-pc> (raw)
In-Reply-To: <CAJPvgrUZR0RymvwqtsPzZRmY5O-HtywEDwpmYQVDxKxffm2kFg@mail.gmail.com>
On Fri, 29 Sep 2017, Marek Twardochlib wrote:
> Hello,
>
> in the current, fresh Emacs 25.3.1 the bug still exist. It would be so
> very nice when someone could fix that. I use macro calls from maco
> very often and this bug prevent this.
Hi,
Emacs 25.3.1 was an emergency release to fix a security vulnerability.
The fix for this bug was included in the master branch at that time; that
means you will see the fix once Emacs 26.1 be released. I think you
don't need to wait very long to see that release: i guess people are
planning to release it soon.
Regards,
Tino
prev parent reply other threads:[~2017-09-29 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 9:23 bug#25860: 25.1; Double macro execution Marek Twardochlib
2017-02-24 14:10 ` Andreas Schwab
2017-02-25 5:41 ` Tino Calancha
2017-02-25 10:10 ` Tino Calancha
2017-02-25 13:27 ` npostavs
2017-02-25 14:48 ` Tino Calancha
2017-02-25 15:26 ` Marek Twardochlib
2017-02-26 5:04 ` Tino Calancha
2017-02-26 7:12 ` npostavs
2017-02-26 15:33 ` Eli Zaretskii
2017-02-26 16:02 ` npostavs
2017-02-27 15:57 ` Eli Zaretskii
2017-02-27 17:18 ` Noam Postavsky
2017-03-03 14:21 ` Eli Zaretskii
2017-09-29 10:29 ` Marek Twardochlib
2017-09-29 11:41 ` Tino Calancha [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=alpine.DEB.2.20.1709292036310.26321@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25860@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jwiegley@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@linux-m68k.org \
--cc=wasserwerk.studio@googlemail.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.