From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Please help me debug my Emacs initialization file
Date: Mon, 29 Jan 2024 14:08:50 +0200 [thread overview]
Message-ID: <86jzns4a0d.fsf@gnu.org> (raw)
In-Reply-To: <CAG9ihEvbv5Bx=4bRUT4qkTcXxbbBXtaYeCPtor24i329dN5KGA@mail.gmail.com> (message from Davin Pearson on Mon, 29 Jan 2024 11:20:07 +1300)
> From: Davin Pearson <davin.pearson@gmail.com>
> Date: Mon, 29 Jan 2024 11:20:07 +1300
>
> Here is the file ~/Binaries/runmacs that I use for loading emacs
>
> !/bin/bash
> date
> cd ~/Downloads/emacs-29.1/src && ./emacs -q --eval "(setq debug-on-error
> t)" --debug-init --load "~/java-training-wheels/dmp-emacs--no-init-file.el"
> &
>
> Here is a tarball for you to load and execute:
>
> http://davin.50webs.com/java-training-wheels.tar.gz
>
> Extract the tarball:
> cd && tar fvx java-training-wheels.tar.gz
>
> Here is the error message that occurs when you run it:
>
> byte-code: Recursive ‘require’ for feature ‘semantic’
>
> This error occurs immediately after the checkpoint:
>
> &safe-require:15014:
>
> in the file ~/java-training-wheels/dlisp/new-code/dmp-safe--require.el.
> It gives similar error messages when you execute the following commands:
>
> C-x C-f
> M-/
> M-.
> C-h a
> C-s
>
> Why doesn't it show a backtrace since I have --debug-init on the command
> line?
Try removing the '--eval "(setq debug-on-error t)"' part from the
command line. --debug-init arranges to report errors while loading
the init file, but setting debug-on-error to a non-default value
causes it to disable its smarts, since it assumes that the user knew
what they were doing.
next prev parent reply other threads:[~2024-01-29 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 22:20 Please help me debug my Emacs initialization file Davin Pearson
2024-01-29 0:14 ` Emanuel Berg
2024-01-29 12:08 ` Eli Zaretskii [this message]
2024-01-29 13:18 ` Michael Heerdegen via Users list for the GNU Emacs text editor
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=86jzns4a0d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).