GNU bug report logs - #53856
elisp errors with filename infarmation

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53856 in the body.
You can then email your comments to 53856 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: goncholden <goncholden <at> protonmail.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: elisp errors with filename infarmation
Date: Mon, 07 Feb 2022 17:35:14 +0000

[Message part 1 (text/plain, inline)]

Occasionally my elisp files fail giving errors but with no indications on the file affected.

[Message part 2 (text/html, inline)]

Message #8 received at 53856 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: goncholden <goncholden <at> protonmail.com>
Cc: 53856 <at> debbugs.gnu.org
Subject: Re: bug#53856: elisp errors with filename infarmation
Date: Tue, 08 Feb 2022 07:14:00 +0100

goncholden <goncholden <at> protonmail.com> writes:

> Occasionally my elisp files fail giving errors but with no indications on the file
> affected.

Can you give an example of such an error message?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #13 received at 53856 <at> debbugs.gnu.org (full text, mbox):

From: goncholden <goncholden <at> protonmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 53856 <at> debbugs.gnu.org
Subject: Re: bug#53856: elisp errors with filename infarmation
Date: Tue, 08 Feb 2022 06:36:25 +0000

------- Original Message -------
On Tuesday, February 8th, 2022 at 6:14 AM, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> goncholden goncholden <at> protonmail.com writes:
>
> > Occasionally my elisp files fail giving errors but with no indications on the file
> > affected.
>
> Can you give an example of such an error message?

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.

Message #16 received at 53856 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: goncholden <goncholden <at> protonmail.com>
Cc: 53856 <at> debbugs.gnu.org
Subject: Re: bug#53856: elisp errors with filename infarmation
Date: Tue, 08 Feb 2022 07:44:22 +0100

goncholden <goncholden <at> 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)?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #19 received at 53856 <at> debbugs.gnu.org (full text, mbox):

From: goncholden <goncholden <at> protonmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 53856 <at> debbugs.gnu.org
Subject: Re: bug#53856: elisp errors with filename infarmation
Date: Tue, 08 Feb 2022 07:01:36 +0000

------- Original Message -------
On Tuesday, February 8th, 2022 at 6:44 AM, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> goncholden goncholden <at> 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)

Message #22 received at 53856 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: goncholden <goncholden <at> protonmail.com>
Cc: 53856 <at> debbugs.gnu.org
Subject: Re: bug#53856: elisp errors with filename infarmation
Date: Wed, 09 Feb 2022 08:59:23 +0100

goncholden <goncholden <at> protonmail.com> writes:

>> > 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)

If you do what the message says -- use --debug-init -- it'll spit out a
backtrace that will tell you where the error occurs.

So I don't think there's anything much to fix here, and I'm therefore
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.