From: Sebastian Wiesner <swiesner@lunaryorn.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Flycheck reports are never satisfying!?
Date: Fri, 29 Aug 2014 11:01:53 +0200 [thread overview]
Message-ID: <1AD23D70-3650-4985-911F-5FA1C2209876@lunaryorn.com> (raw)
In-Reply-To: <jwvegw07h3g.fsf-monnier+gmane.emacs.help@gnu.org>
Am 28.08.2014 um 17:48 schrieb Stefan Monnier <monnier@iro.umontreal.ca>:
>> Isn’t that what we have „with-eval-after-load“ for?
>
> with-eval-after-load is there to help make startup more lazy. But it's
> not particularly designed to help silence "spurious" byte-compiler warnings.
>
>> At least, that’s what I am using in my init.el to avoid warnings about
>> free variables.
>
> I'm surprised it works for you.
I'm sorry, it doesn't, of course. I mistakenly assumed that with-eval-after-load did that, but actually I'm using my own macro on top of with-eval-after-load that requires the given feature during byte compilation. I forgot about that.
Please excuse the confusion.
>
> This said, maybe the byte-compiler should treat it specially
> (i.e. treat it sort of like a `require' and forcefully load the file
> before processing the body of the with-eval-after-load).
Couldn't with-eval-after-load just require the feature if byte-compile-current-file is non-nil?
At least, that's what I am doing in my own macro, and it works reasonably well.
next prev parent reply other threads:[~2014-08-29 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 12:05 Flycheck reports are never satisfying!? Sebastien Vauban
2014-08-28 13:40 ` Stefan Monnier
2014-08-28 15:15 ` Sebastian Wiesner
2014-08-28 15:48 ` Stefan Monnier
2014-08-29 9:01 ` Sebastian Wiesner [this message]
2014-08-29 13:05 ` Stefan Monnier
[not found] ` <mailman.7732.1409240949.1147.help-gnu-emacs@gnu.org>
2014-08-28 17:35 ` Sebastien Vauban
2014-08-29 3:32 ` Stefan Monnier
[not found] ` <mailman.7720.1409233288.1147.help-gnu-emacs@gnu.org>
2014-08-28 14:14 ` Sebastien Vauban
2014-08-28 14:38 ` Stefan Monnier
2014-08-28 15:51 ` worrying about byte-compiler warnings [was: Flycheck reports are never satisfying!?] Drew Adams
2014-08-28 15:25 ` Flycheck reports are never satisfying!? Sebastian Wiesner
[not found] ` <61C65218-4004-4FD5-ABE0-6C863E5F60A6-MMJ3jE1zGgOaMJb+Lgu22Q@public.gmane.org>
2014-08-28 15:39 ` Sebastien Vauban
2014-08-28 15:45 ` Sebastian Wiesner
[not found] ` <B540BE8A-D03C-4F2D-ADB7-2A17F8E55F4E-MMJ3jE1zGgOaMJb+Lgu22Q@public.gmane.org>
2014-08-28 18:35 ` Sebastien Vauban
[not found] ` <mailman.7753.1409250970.1147.help-gnu-emacs@gnu.org>
[not found] ` <mailman.7753.1409250970.1147.help-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-09-01 10:00 ` Sebastien Vauban
2014-09-01 10:23 ` Sebastian Wiesner
2014-09-01 12:27 ` sokobania.01
2014-09-01 12:30 ` sokobania.01
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1AD23D70-3650-4985-911F-5FA1C2209876@lunaryorn.com \
--to=swiesner@lunaryorn.com \
--cc=help-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.