From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: 65267@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken
Date: Sun, 13 Aug 2023 15:47:33 -0400 [thread overview]
Message-ID: <jwvr0o6pww4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20230813190826+0200.765169-stepnem@smrk.net> ("Štěpán Němec"'s message of "Sun, 13 Aug 2023 19:08:26 +0200")
[ Added Noam, since we're mentioning a problem linked to yasnippet.el. ]
>> Yeah, it's wrong, but I'm not sure how to fix it:
>> `--debug-init` needs to change the value of `debug-ignored-errors` while
>> `init.el` is executed,
>
> FWIW, I'm sure I'm missing something, but the above is far from obvious
> to me. Why does --debug-init need to muck with debug-ignored-errors at
> all? debug-ignored-errors usually/mostly contains errors unlikely to
> occur during startup,
"unlikely" doesn't mean they should be ignored: `debug-ignored-errors`
is for errors which should not bring up a debugger if they occur in
interactive use, but they're still errors, and if they occur during
`init.el` they are definitely not ignored: they stop the processing of
`init.el`. So when debugging init errors, we *should* bring up the
debugger for them.
>> Maybe we should introduce a new `inhibit-debug-ignored-errors` which we
>> could let-bind while loading `init.el` without having to modify
>> `debug-ignored-errors` itself?
>
> If ignoring debug-ignored-errors during startup is really necessary,
> that sounds like a possibly cleaner way, indeed
..
> (albeit introducing yet another form to ignore another form ignoring
> errors...).
Yes, that's what's making me hesitate.
>> We could document that modifying debug-ignored-errors only works
>> reliably if done from after-init-hook. WDYT?
>
> Pushing the breakage downstream... would mean packages like yasnippet
> would have to adapt, among other things. Not the end of the world, I
> guess, but I still don't understand why the breakage (or "change in
> behavior", if you prefer) is necessary or desired.
Hmm... thanks for pointing out that left-over thingy in `yasnippet.el`
which should have been removed as part of:
commit 175e0a3a102c22c0c99d8d00ecf8bc8539a4e593
Author: João Távora <joaotavora@gmail.com>
Date: Mon Nov 17 11:27:30 2014 +0000
Clean up previous change
* yasnippet.el: Update comment.
(yas--protection-violation): Removed.
(yas--on-protection-overlay-modification): Simplified.
(yas--post-command-handler): No longer reference
`yas--protection-violation'
I pushed a commit to clean this up to the `scratch/yasnippet` branch of
elpa.git.
Stefan
next prev parent reply other threads:[~2023-08-13 19:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 7:54 bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken Štěpán Němec
2023-08-13 9:49 ` Eli Zaretskii
2023-08-13 10:03 ` Štěpán Němec
2023-08-13 10:12 ` Eli Zaretskii
2023-08-13 10:24 ` Štěpán Němec
2023-08-13 12:38 ` Eli Zaretskii
2023-08-13 16:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-13 16:32 ` Eli Zaretskii
2023-08-13 17:08 ` Štěpán Němec
2023-08-13 17:52 ` Eli Zaretskii
[not found] ` <20230813203525+0200.956511-stepnem@smrk.net>
2023-08-13 19:05 ` Eli Zaretskii
2023-08-13 19:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <20230813223458+0200.843367-stepnem@smrk.net>
2023-08-14 2:26 ` Eli Zaretskii
2023-08-14 6:48 ` Štěpán Němec
2023-08-17 9:31 ` Eli Zaretskii
2023-08-17 12:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 13:28 ` Eli Zaretskii
2023-08-17 14:16 ` Štěpán Němec
2023-08-17 14:31 ` Eli Zaretskii
2023-08-17 14:36 ` Eli Zaretskii
2023-08-17 15:52 ` bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken, " Štěpán Němec
2023-08-17 16:05 ` Eli Zaretskii
2023-08-17 16:29 ` Štěpán Němec
2023-08-17 17:58 ` Eli Zaretskii
2023-08-17 18:15 ` Štěpán Němec
2023-08-17 18:36 ` Eli Zaretskii
2023-08-17 17:15 ` Gregory Heytings
2023-08-17 17:27 ` Štěpán Němec
2023-08-17 18:07 ` Gregory Heytings
2023-08-17 18:20 ` Štěpán Němec
2023-08-17 18:31 ` Gregory Heytings
2023-08-17 18:36 ` Štěpán Němec
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=jwvr0o6pww4.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=65267@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
--cc=stepnem@smrk.net \
/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).