[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Flycheck reports are never satisfying!?
From: |
Sebastian Wiesner |
Subject: |
Re: Flycheck reports are never satisfying!? |
Date: |
Thu, 28 Aug 2014 17:15:13 +0200 |
Am 28.08.2014 um 15:40 schrieb Stefan Monnier <monnier@iro.umontreal.ca>:
>> --8<---------------cut here---------------start------------->8---
>> 25 9 warning assignment to free variable `flycheck-indication-mode'
>> (emacs-lisp)
>> --8<---------------cut here---------------end--------------->8---
>
> The .emacs file is very much unlike a normal Elisp package: instead of
> defining its own functions/command/variables and exporting them for use,
> it normally does mostly things like modifying other
> package's variables.
>
> And those packages are usually not loaded yet, because we want to load
> them lazily to speed up startup.
>
> So yes, if you try to byte-compile your .emacs chances are the
> byte-compiler will give you lots and lots of warnings about assignments
> or references to free variables.
>
> That's a problem I'd like to fix, but I'm not completely sure how.
> Suggestions welcome,
Isn’t that what we have „with-eval-after-load“ for? At least, that’s what I am
using in my init.el to avoid warnings about free variables.
Message not available
Re: Flycheck reports are never satisfying!?, Sebastian Wiesner, 2014/08/28