From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
leungbk@mailfence.com, emacs-devel@gnu.org
Subject: Re: master cfcf42f 2/2: Ensure that gud commands for non-GDB debuggers are handled by repeat-mode
Date: Fri, 30 Jul 2021 18:08:02 -0400 [thread overview]
Message-ID: <jwvfsvvfoir.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r1ffit6k.fsf@mail.linkov.net> (Juri Linkov's message of "Fri, 30 Jul 2021 20:54:11 +0300")
Juri Linkov [2021-07-30 20:54:11] wrote:
> For example, today's compilation displayed as lot of such lines:
>
> Warning: Eager macro-expansion skipped due to cycle:
> … => (load "byte-opt.el") => (macroexpand-all …
> Warning: Eager macro-expansion skipped due to cycle:
> … => (load "byte-opt.el") => (macroexpand-all …
> …
These usually reflect bugs, but we can't conveniently pin them on
a particular file (they're usually due to a cycle between macros and
functions in several files), so I don't think using the standard
"<FILE>:<FOO>" syntax for warnings would be all that useful, but it
wouldn't make things worse either, so a "<FILE>:0:" prefix sounds like
a good idea (where <FILE> would presumably be the file we're eagerly
macroexpanding).
Sometimes they're highly dependent on specific ordering of compilation
of files, but if you can reproduce them reliably, then please report
them so we can try and fix them.
Stefan
next prev parent reply other threads:[~2021-07-30 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210727211521.15408.98852@vcs0.savannah.gnu.org>
[not found] ` <20210727211523.AE6F72065F@vcs0.savannah.gnu.org>
2021-07-28 15:40 ` master cfcf42f 2/2: Ensure that gud commands for non-GDB debuggers are handled by repeat-mode Lars Ingebrigtsen
2021-07-28 16:24 ` Juri Linkov
2021-07-28 16:35 ` Lars Ingebrigtsen
2021-07-28 16:49 ` Juri Linkov
2021-07-29 20:13 ` Lars Ingebrigtsen
2021-07-29 22:43 ` Juri Linkov
2021-07-30 10:53 ` Lars Ingebrigtsen
2021-07-30 17:51 ` Juri Linkov
2021-07-30 18:13 ` Lars Ingebrigtsen
2021-07-30 5:43 ` Eli Zaretskii
2021-07-30 10:55 ` Lars Ingebrigtsen
2021-07-30 11:03 ` Eli Zaretskii
2021-07-30 11:16 ` Lars Ingebrigtsen
2021-07-30 12:13 ` Eli Zaretskii
2021-07-30 12:20 ` Lars Ingebrigtsen
2021-07-30 13:22 ` Eli Zaretskii
2021-07-30 14:39 ` Lars Ingebrigtsen
2021-07-30 17:54 ` Juri Linkov
2021-07-30 18:26 ` Eli Zaretskii
2021-07-30 22:08 ` Stefan Monnier [this message]
2021-07-30 22:03 ` Stefan Monnier
2021-08-01 8:32 ` Juri Linkov
2021-08-01 10:42 ` Lars Ingebrigtsen
2021-08-01 14:28 ` Stefan Monnier
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=jwvfsvvfoir.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=leungbk@mailfence.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).