From: Heime <heimeborgia@protonmail.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Initialization warnings without compehensive information about problem
Date: Tue, 15 Nov 2022 16:48:02 +0000 [thread overview]
Message-ID: <b6dSFiXaLRLxaeXkCXg8sRHE173fMPnDtUe6GfMMKtKv2UgTYfWLEOV28bSx91p6abgxHd34VxTiJsSljIxPFh_4l3P4gabaM3yU55K7RCI=@protonmail.com> (raw)
In-Reply-To: <874jv2g9qn.fsf@dataswamp.org>
------- 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.
next prev parent reply other threads:[~2022-11-15 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 10:34 Initialization warnings without compehensive information about problem Heime
2022-11-13 11:19 ` Emanuel Berg
2022-11-13 14:00 ` Bruno Barbier
2022-11-13 14:57 ` Heime
2022-11-13 15:17 ` Bruno Barbier
2022-11-13 15:22 ` Emanuel Berg
2022-11-15 16:48 ` Heime [this message]
2022-11-15 17:56 ` Bruno Barbier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b6dSFiXaLRLxaeXkCXg8sRHE173fMPnDtUe6GfMMKtKv2UgTYfWLEOV28bSx91p6abgxHd34VxTiJsSljIxPFh_4l3P4gabaM3yU55K7RCI=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).