* bug#53856: elisp errors with filename infarmation
@ 2022-02-07 17:35 goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 6:14 ` Lars Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-02-07 17:35 UTC (permalink / raw)
To: 53856
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#53856: elisp errors with filename infarmation
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
0 siblings, 1 reply; 6+ messages in thread
From: Lars Ingebrigtsen @ 2022-02-08 6:14 UTC (permalink / raw)
To: goncholden; +Cc: 53856
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#53856: elisp errors with filename infarmation
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
0 siblings, 1 reply; 6+ messages in thread
From: goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-02-08 6:36 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 53856
------- 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#53856: elisp errors with filename infarmation
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
0 siblings, 1 reply; 6+ messages in thread
From: Lars Ingebrigtsen @ 2022-02-08 6:44 UTC (permalink / raw)
To: goncholden; +Cc: 53856
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#53856: elisp errors with filename infarmation
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
2022-02-09 7:59 ` Lars Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-02-08 7:01 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 53856
------- 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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#53856: elisp errors with filename infarmation
2022-02-08 7:01 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2022-02-09 7:59 ` Lars Ingebrigtsen
0 siblings, 0 replies; 6+ messages in thread
From: Lars Ingebrigtsen @ 2022-02-09 7:59 UTC (permalink / raw)
To: goncholden; +Cc: 53856
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-02-09 7:59 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2022-02-09 7:59 ` Lars Ingebrigtsen
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).