From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 55811@debbugs.gnu.org
Subject: bug#55811: 29.0.50; No flymake diagnostics for no-byte-compile files
Date: Tue, 07 Jun 2022 07:47:24 -0400 [thread overview]
Message-ID: <jwv35ggn1gx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k09t561m.fsf@gmail.com> ("João Távora"'s message of "Tue, 07 Jun 2022 07:41:41 +0100")
> Of course you know this -- but just to clarify -- the byte-compilation
> backend works by launching a Emacs -Q which is asked to byte-compile
> only a file containing the current buffer's contents. During that
> byte-compilation nothing more is loaded apart from what is preloaded or
> explicitly loaded by the file at compile-time (via require or
> eval-when/and-compile stuff).
This bug-report is about the fact that there is no benefit to
obeying `no-byte-compile` in flymake. Not about improving the way the
sub-process reproduces a "good" initial state to compile the file
(e.g. set up of `load-path` and whatnot).
> Anyway, maybe you could give small example of such a file containing
> such a cookie where you think Flymake's "I refuse to lint this" behavior
> could be improved.
A good example are all the files in the
[EEV](http://elpa.gnu.org/packages/eev.html) package.
Stefan
next prev parent reply other threads:[~2022-06-07 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 20:22 bug#55811: 29.0.50; No flymake diagnostics for no-byte-compile files Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 20:33 ` Lars Ingebrigtsen
2022-06-05 23:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-06 12:40 ` Lars Ingebrigtsen
2022-06-07 6:41 ` João Távora
2022-06-07 11:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-07 11:54 ` Lars Ingebrigtsen
2022-06-07 12:13 ` João Távora
2022-06-07 13:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 12:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 12:42 ` Lars Ingebrigtsen
2022-06-07 13:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 12:02 ` João Távora
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=jwv35ggn1gx.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=55811@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.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).