Re: Initialization warnings without compehensive information about problem

[Heime]

------- Original Message -------
On Sunday, November 13th, 2022 at 3:22 PM, Emanuel Berg <incal@dataswamp.org> 
wrote:


> Bruno Barbier wrote:
> 
> > > It would be more useful for the "Warnings" to give good
> > > information rather than the generic .emacs has a problem
> > > with a function definition being void. It is a bother that
> > > for any problem one has to rerun again with "--debug-init".
> > 
> > You just need to always start emacs with '--debug-init', if
> > you really want Emacs to always immediately stop on any
> > config issue.
> 
> 
> But that's 0.018 seconds slower ...
> 
> $ time emacs -f kill-emacs
> emacs -f kill-emacs 2.16s user 0.21s system 84% cpu 2.809 total
> 
> $ time emacs --debug-init -f kill-emacs
> emacs --debug-init -f kill-emacs 2.23s user 0.19s system 85% cpu 2.826 total

I would be far more convenient if the "*Warnings*" could provide a little bit
more information about the problem.  Not at the level of --debug-init or
byte-compilation, some something one can act on.