unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sebastian Miele <iota@whxvd.name>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64163@debbugs.gnu.org
Subject: bug#64163: 29.0.92; Syntactic errors in early init when --debug-init is on
Date: Tue, 20 Jun 2023 16:27:24 +0300	[thread overview]
Message-ID: <83y1ke5kn7.fsf@gnu.org> (raw)
In-Reply-To: <878rcf20l0.fsf@whxvd.name> (message from Sebastian Miele on Mon,  19 Jun 2023 12:27:09 +0200)

> From: Sebastian Miele <iota@whxvd.name>
> Date: Mon, 19 Jun 2023 12:27:09 +0200
> 
> Create a $DIR with an early-init.el containing just '(' and an init.el
> with just '(error "Later")'.
> 
> Then running
> 
>   src/emacs --init-directory=$DIR
> 
> produces a warning buffer that lists both errors in order.  However,
> when running
> 
>   src/emacs --init-directory=$DIR --debug-init
> 
> the debugger triggers on the error "Later", without any mention of the
> error in the early init file.  This is unexpected.

First, the --init-directory=$DIR part is not relevant to the issue;
the same happens if you place such init files in your "normal" home
directory.

More to the point, that error in early-init.el does not trigger a
backtrace because 'end-of-file' error is in the list that is the value
of debug-ignored-errors.  So this problem is specific to that
particular kind of error in early-init.el.  If you trigger some other
error, which is not in the list of ignored ones, you will see a
backtrace.

IOW, this is the expected behavior.

I wonder whether the patch below could be the solution to this.
Stefan, WDYT?  Should we perhaps condition this binding by more
conditions, like only do this in interactive invocations or something?

diff --git a/lisp/startup.el b/lisp/startup.el
index b0f019d..bf16f14 100644
--- a/lisp/startup.el
+++ b/lisp/startup.el
@@ -1030,7 +1030,8 @@ startup--load-user-init-file
     (let ((debug-on-error debug-on-error-initial))
       (condition-case-unless-debug error
           (when init-file-user
-            (let ((init-file-name (funcall filename-function)))
+            (let ((init-file-name (funcall filename-function))
+                  (debug-ignored-errors nil))
 
               ;; If `user-init-file' is t, then `load' will store
               ;; the name of the file that it loads into





  reply	other threads:[~2023-06-20 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 10:27 bug#64163: 29.0.92; Syntactic errors in early init when --debug-init is on Sebastian Miele
2023-06-20 13:27 ` Eli Zaretskii [this message]
2023-06-20 14:24   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-20 16:05     ` Eli Zaretskii
2023-06-20 17:07       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 13:29         ` Eli Zaretskii

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=83y1ke5kn7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64163@debbugs.gnu.org \
    --cc=iota@whxvd.name \
    --cc=monnier@iro.umontreal.ca \
    /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).