From: "Štěpán Němec" <stepnem@smrk.net>
To: Gregory Heytings <gregory@heytings.org>
Cc: 65267@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, npostavs@users.sourceforge.net
Subject: bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken, bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken
Date: Thu, 17 Aug 2023 20:20:54 +0200 [thread overview]
Message-ID: <20230817202054+0200.591420-stepnem@smrk.net> (raw)
In-Reply-To: <6ed65a8d103f9c88bd37@heytings.org>
On Thu, 17 Aug 2023 18:07:55 +0000
Gregory Heytings wrote:
>>
>> Thank you, but I believe we all knew that, already.
>>
>
> I apologize for trying to help.
Well, I don't apologize for (*sincerely*) thanking you.
> I'd say that the fact that end-of-file has been in the default value of
> debug-ignored-errors for a quarter of a century without anyone objecting
> indicates that it's a reasonable default. And you can easily remove it
> from there if you want:
>
> (delq 'end-of-file debug-ignored-errors)
Maybe you know something about `delq' I do not, but I always use
something like
(setq debug-ignored-errors (delq 'end-of-file debug-ignored-errors))
instead. (See the documentation of `delq'.)
--
Štěpán
next prev parent reply other threads:[~2023-08-17 18:20 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
[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 [this message]
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=20230817202054+0200.591420-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=65267@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.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).