Prevent `:defer 0.1` packages from loading in batch mode

[aaronjensen]

I tend to think of :defer 0.1 as effectively "load this package after 0.1s of idle time after init. I just learned that this isn't how it works--it actually considers idle time during a batch process to be enough to load the package. I compile my emacs config in a batch process, so what happens is packages I defer end up getting required after the batch process. I guess for now I will do a manual deferral in an after init hook, but it'd be great if defer's semantics were changed or there were a way to specify that I didn't want the idle time to start until after init.

Thanks!

[aaronjensen]

Actually, maybe I'm totally wrong on this. Maybe it's just that during byte compile all configs are evaluated... is that what's going on here?