all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@smrk.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65267@debbugs.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
Date: Mon, 14 Aug 2023 08:48:38 +0200	[thread overview]
Message-ID: <20230814084838+0200.989625-stepnem@smrk.net> (raw)
In-Reply-To: <83r0o6bbqw.fsf@gnu.org>

On Mon, 14 Aug 2023 05:26:15 +0300
Eli Zaretskii wrote:

>> From: Štěpán Němec <stepnem@smrk.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 65267@debbugs.gnu.org, Noam Postavsky
>>  <npostavs@users.sourceforge.net>
>> Date: Sun, 13 Aug 2023 22:34:58 +0200
>> 
>> So, yes, I agree that end-of-file (which indeed isn't unlikely to occur
>> during loading) now ending up in the debugger is an improvement.
>> 
>> Checking git history, I also see that end-of-file has been in
>> debug-ignored-errors since forever, but I still can't rid myself of
>> doubts regarding its usefulness there.  Would you have an explanation
>> for that, too?  Other than it not fitting with the others (IMHO), its
>> absence there would likely save us all this (bug#64163 and the ensuing
>> mess).  I find any of the other members of debug-ignored-errors being
>> triggered during startup much less likely.  (And, OTOH, why would I want
>> to ignore end-of-file during interactive use with d-o-e set?)
>
> It is not ignored, it just doesn't enter the debugger.

That's what I meant, sorry for not being clearer.

Unlike the other members of debug-ignored-errors, end-of-file doesn't
strike me as an error likely to cause annoyance rather than provide
useful backtrace data when running with debug-on-error set, so I don't
understand why it's there by default.  I'll remove it here and see how
that goes.

-- 
Štěpán





  reply	other threads:[~2023-08-14  6:48 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230814084838+0200.989625-stepnem@smrk.net \
    --to=stepnem@smrk.net \
    --cc=65267@debbugs.gnu.org \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.