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 06:36:25 +0000 [thread overview]
Message-ID: <TAXK0Q32dC4usWQchsg3tetMLefCz_h_B0NJr9ungA8GAs159I3bi1QQMhI2h_nLwazvFG4YrKCnkdHOx26Y0F9rPQ97igjXcsxwOlPgXs8=@protonmail.com> (raw)
In-Reply-To: <875yppvqaf.fsf@gnus.org>
------- 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.
next prev parent reply other threads:[~2022-02-08 6:36 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 [this message]
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
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='TAXK0Q32dC4usWQchsg3tetMLefCz_h_B0NJr9ungA8GAs159I3bi1QQMhI2h_nLwazvFG4YrKCnkdHOx26Y0F9rPQ97igjXcsxwOlPgXs8=@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).