unofficial mirror of bug-gnu-emacs@gnu.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, bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken
Date: Thu, 17 Aug 2023 17:52:59 +0200	[thread overview]
Message-ID: <20230817175259+0200.372333-stepnem@smrk.net> (raw)
In-Reply-To: <83bkf568rf.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Aug 2023 17:31:00 +0300, Thu, 17 Aug 2023 17:36:09 +0300")

On Thu, 17 Aug 2023 17:31:00 +0300
Eli Zaretskii wrote:

>> From: Štěpán Němec <stepnem@smrk.net>
>> Cc: 65267@debbugs.gnu.org, npostavs@users.sourceforge.net
>> Date: Thu, 17 Aug 2023 16:16:19 +0200
>> 
>> On Thu, 17 Aug 2023 16:28:31 +0300
>> Eli Zaretskii wrote:
>> 
>> Your patch preserves additions (although it moves them to the end of the
>> list, but that shouldn't matter for debug-ignored-errors), but doesn't
>> preserve removals
>
> If someone want to remove from the list, and use --debug-init on top
> of that, they will need to replace the value instead.  If that's the
> only downside of the patch I proposed, I think people will be able to
> live with it.

As you said, debug-ignored-errors is a user variable.  So some people
are likely to change it, and some (most?) of those people will do that
from their init file.  I don't see how adding vs removing is any
different in that respect.

As for --debug-init, why would anyone (who knows about that option and
cares about their setup) routinely start Emacs *without* it?

>> Have you considered my humble suggestion of reverting to pre-bug#64163
>> state and simply removing end-of-file from the default value of
>> debug-ignored-errors?
>
> Yes.  This cannot fly, since we had end-of-file there for a long time
> (I see it in Emacs 20).

I only wish someone would put forth an actual argument for having
end-of-file on debug-ignored-errors.

I agree backward compatibility/preserving behavior is important, but I
hope you'll agree that some behavior changes are more
serious/visible/disruptive/whatever than others, and I'd argue that in
that sense, messing with user option modification during startup is a
worse change than removing end-of-file from debug-ignored-errors.

So if we're again back to blessing the breakage, I suggest it at least
be documented.

On Thu, 17 Aug 2023 17:36:09 +0300
Eli Zaretskii wrote:

>> Cc: 65267@debbugs.gnu.org, monnier@iro.umontreal.ca,
>>  npostavs@users.sourceforge.net
>> Date: Thu, 17 Aug 2023 17:31:00 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> > Have you considered my humble suggestion of reverting to pre-bug#64163
>> > state and simply removing end-of-file from the default value of
>> > debug-ignored-errors?
>> 
>> Yes.  This cannot fly, since we had end-of-file there for a long time
>> (I see it in Emacs 20).
>
> And, of course, end-of-file is just one of the errors in the list;
> bug#64163 could have been equally reported with any of those other
> ones, and the solution is the same.

"Equally" I don't think.  If it took many (tens of?) years for anybody
to be bothered by the end-of-file case (bug#64163), which IME indeed
occurs somewhat regularly during startup (missing closing paren), I find
the same happening with any of the other members of debug-ignored-errors
exceedingly unlikely.

I agree with Stefan that no good solution has so far emerged.  The
advantage of my suggestion would be that it only changes
debug-ignored-errors in a way that makes sense anyway (in absence of any
arguments to the contrary), preventing bug#64163 as a byproduct, rather
than adding to convoluted code nobody involved seems to really
understand in a way that nobody involved seems to really understand or
expect.

-- 
Štěpán





  parent reply	other threads:[~2023-08-17 15:52 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                 ` Štěpán Němec [this message]
2023-08-17 16:05                   ` bug#65267: 30.0.50; modifying debug-ignored-errors during startup with --debug-init is broken, " 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=20230817175259+0200.372333-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 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).