From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 55811@debbugs.gnu.org
Subject: bug#55811: 29.0.50; No flymake diagnostics for no-byte-compile files
Date: Tue, 07 Jun 2022 13:13:42 +0100 [thread overview]
Message-ID: <877d5s658p.fsf@gmail.com> (raw)
In-Reply-To: <877d5sk7sj.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 07 Jun 2022 13:54:52 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> This bug-report is about the fact that there is no benefit to
>> obeying `no-byte-compile` in flymake.
>
> Well, there are some. If you open, say, lisp/net/tramp-loaddefs.el,
> you'll get a whole bunch of compilation errors, and you don't want to
> see those, I think?
They could be useful I guess. There are two cases to distinguish here
(which is what I failed to clarify before). Perhaps Stefan is thinking
of the second.
1. The file has this form:
(require 'foo)
(fooey-macro (some-shady-stuff-the-byte-comp-could-look-into))
(some-more-shady-stuff)
;; Local Variables:
;; no-byte-compile: t
;; End:
and the reason for adding the no-byte-compile cookie is that foo.el
can't be found at compile-time. Then I think there is little reason
to activate Flymake there. That's because Flymake will halt at the
(require 'foo) and not look into the rest of the file.
2. The file is identical but doesn't have the (require 'foo), then, I
think Flymake will underline the first form, but carry on looking
into other stuff. This is possibly helpful, according to one's
own tolerance of signal-to-noise ratio.
If some files in case 2 are still unbearably noisy for some, then I
think there are existing ways to force Flymake off using buffer-local
variables.
João
next prev parent reply other threads:[~2022-06-07 12:13 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
2022-06-07 11:54 ` Lars Ingebrigtsen
2022-06-07 12:13 ` João Távora [this message]
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=877d5s658p.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=55811@debbugs.gnu.org \
--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).