From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53856@debbugs.gnu.org
Subject: bug#53856: elisp errors with filename infarmation
Date: Tue, 08 Feb 2022 07:01:36 +0000 [thread overview]
Message-ID: <WTV3l3zVQ49xa4CUB_I4hdGN6Eaq3t6JcH0_wK04xAk7PHd_2kt-HI9-NT0i0F-YdtgrI1en-_4P39L8ilTmrjMa98zhTQayO-MSMhMhe9c=@protonmail.com> (raw)
In-Reply-To: <87zgn1svqx.fsf@gnus.org>
------- Original Message -------
On Tuesday, February 8th, 2022 at 6:44 AM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> goncholden goncholden@protonmail.com writes:
>
> > For instance, I have a file that defines a minor-mode. Introducing an arbitrary
> > string "idi" on a line by itself, I get the following warning
> > Warning (initialization): An error occurred while loading
> > ‘/home/hagbard/.emacs’:
> > Symbol's value as variable is void: idi
> > To ensure normal operation, you should investigate and remove the
> > cause of the error in your initialization file. Start Emacs with
> > the ‘--debug-init’ option to view a complete error backtrace.
> You want Emacs to say that the error was in whatever file you're loading
> instead of where the error appears (which is ~/.emacs, which Emacs
> reports)?
~/.emacs launches elisp files using the function typex-launch (which calls additional init files,
minor-modes, modified elisp packages, ...)
For instance, ~/.emacs includes
(add-to-list 'load-path "/home/hagbard/Opstk/bin/typex/")
(load "typex")
(typex-launch)
next prev parent reply other threads:[~2022-02-08 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 17:35 bug#53856: elisp errors with filename infarmation goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 6:14 ` Lars Ingebrigtsen
2022-02-08 6:36 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 6:44 ` Lars Ingebrigtsen
2022-02-08 7:01 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-09 7:59 ` Lars Ingebrigtsen
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='WTV3l3zVQ49xa4CUB_I4hdGN6Eaq3t6JcH0_wK04xAk7PHd_2kt-HI9-NT0i0F-YdtgrI1en-_4P39L8ilTmrjMa98zhTQayO-MSMhMhe9c=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=53856@debbugs.gnu.org \
--cc=goncholden@protonmail.com \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).