Subject: Re: bug#55811: 29.0.50; No flymake diagnostics for no-byte-compile files

From: Stefan Monnier <[email-masked]>
Date: Tue, 07 Jun 2022 09:46:35 -0400

> 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.

BTW, while there is little benefit to having flymake run the
byte-compiler here, there is similarly little harm.
And the user may then decide to install `foo` to get the rest of the
file properly checked.

        Stefan