From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 47049@debbugs.gnu.org
Subject: bug#47049: [feature/native] macro-expansion cycle when compiling comp.el
Date: Fri, 12 Mar 2021 21:37:23 +0000 [thread overview]
Message-ID: <xjfh7lg12b0.fsf@sdf.org> (raw)
In-Reply-To: <jwvpn04cbd4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 12 Mar 2021 16:26:54 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Yep that's what I attemped and reported in the other mail, I guess our
>> mails crossed over the ocean.
>
> I think it was *under* the ocean...
Right! I pushed through the underside of the ocean d018584814 that is
fixing this for me.
Eli please have a look if it works for you.
Thanks!
Andrea
next prev parent reply other threads:[~2021-03-12 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 13:59 bug#47049: [feature/native] macro-expansion cycle when compiling comp.el Eli Zaretskii
2021-03-10 16:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-10 16:17 ` Eli Zaretskii
2021-03-11 15:26 ` Stefan Monnier
2021-03-12 20:02 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 20:55 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 21:05 ` Stefan Monnier
2021-03-12 21:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 21:26 ` Stefan Monnier
2021-03-12 21:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-13 7:50 ` Eli Zaretskii
2021-03-12 15:05 ` Eli Zaretskii
2021-03-12 15:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfh7lg12b0.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47049@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).