bug#53856: elisp errors with filename infarmation

bug#53856: elisp errors with filename infarmation

[goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors]

[-- Attachment #1: Type: text/plain, Size: 92 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 556 bytes --]

bug#53856: elisp errors with filename infarmation

[Lars Ingebrigtsen]

goncholden <goncholden@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

bug#53856: elisp errors with filename infarmation

[goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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

bug#53856: elisp errors with filename infarmation

[Lars Ingebrigtsen]

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

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

bug#53856: elisp errors with filename infarmation

[goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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

bug#53856: elisp errors with filename infarmation

[Lars Ingebrigtsen]

goncholden <goncholden@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