redguardtoo / emacs.d

Fast and robust Emacs setup.
http://blog.binchen.org
GNU General Public License v3.0
2.39k stars 619 forks source link

When I set byte-compile-warnings globaly, it not working for flymake. #1038

Closed sbwcwso closed 1 year ago

sbwcwso commented 1 year ago

I put this sentence in my init.el (setq byte-compile-warnings '(not free-vars unresolved)), but the flymake will still warning.

image

redguardtoo commented 1 year ago

That's ok . You can ignore those warnings.

BTW, byte compile your "emacs.d" won't speed up emacs and could bring more trouble (you changed your emacs.d but forgot to compile the latest init.el). I remember I wrote some article about this issue.

sbwcwso commented 1 year ago

That's ok . You can ignore those warnings.

BTW, byte compile your "emacs.d" won't speed up emacs and could bring more trouble (you changed your emacs.d but forgot to compile the latest init.el). I remember I wrote some article about this issue.

But when I put the follow code in the init.el, there is no such warning in the flaymake intermately.

;; Local Variables:
;; byte-compile-warnings: (not free-vars unresolved callargs)
;; End:

I get this from https://emacs.stackexchange.com/a/19507