From: Heime <heimeborgia@protonmail.com>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Initialization warnings without compehensive information about problem
Date: Sun, 13 Nov 2022 14:57:47 +0000 [thread overview]
Message-ID: <d0qt28-svP0ddFPdY6Zq_nAMH028joaeBxDGl7RwinH_A9I6VKEM8Pah4U-5VfstvOT89mAQ6m1-Al0WYxe6UzQ83zS6ipIBnS1bJqHgaN4=@protonmail.com> (raw)
In-Reply-To: <6370f707.050a0220.24053.6515@mx.google.com>
------- Original Message -------
On Sunday, November 13th, 2022 at 1:55 PM, Bruno Barbier <brubar.cs@gmail.com> wrote:
> Heime heimeborgia@protonmail.com writes:
>
> > I do not like that when there is a problem the "Warnings" buffer only says
> >
> > Warning (initialization): An error occurred while loading ‘/home/hagbard/.emacs’:
> > Symbol's function definition is void: wordscal-ktrigr
> >
> > Providing little useful information regarding the file, its location and the corresponding
> > line number where the problem was detected.
>
>
> You need to start Emacs with the "--debug-init". That way, it will stop
> and give you all the details about the error.
>
> See (info "(emacs) Initial Options")
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".
next prev parent reply other threads:[~2022-11-13 14:57 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 [this message]
2022-11-13 15:17 ` Bruno Barbier
2022-11-13 15:22 ` Emanuel Berg
2022-11-15 16:48 ` Heime
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='d0qt28-svP0ddFPdY6Zq_nAMH028joaeBxDGl7RwinH_A9I6VKEM8Pah4U-5VfstvOT89mAQ6m1-Al0WYxe6UzQ83zS6ipIBnS1bJqHgaN4=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=brubar.cs@gmail.com \
--cc=help-gnu-emacs@gnu.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).