From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36903@debbugs.gnu.org
Subject: bug#36903: 27.0.50; gnus registry vs. debbugs
Date: Sun, 15 Sep 2019 08:27:43 +0800 [thread overview]
Message-ID: <87v9tuh08w.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874l1e7wcq.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 14 Sep 2019 17:04:21 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>> I can't really imagine it being performance-related... computing the
>>> specs take extremely little time.
>>>
>>> But it's possible, I guess.
>>
>> I'll patch locally and run it for a while.
>
> So I think we arrived at the conclusion that removing that removal
> should be safe (i.e., a noop) -- did you apply the patch?
I didn't, because it doesn't solve anything, and it seemed like a proper
fix would probably include this.
> I'm not sure how this related to the other registry stuff... What was
> the conclusion there?
The conclusion is I don't know what to do. Users who have customized
`gnus-summary-line-format' to draw info from the registry will see an
error if they start Gnus, stop Gnus, then start debbugs-gnu. That's
because stopping Gnus clears the registry, but starting debbugs-gnu
doesn't re-load it (because it doesn't load the users gnus.el file), and
the summary line format continues trying to access the registry object.
I naively tried *adding* `gnus-format-specs' to the list of variables to
clear, but of course that doesn't work because
`gnus-summary-line-format' remains customized, and `gnus-format-specs'
is simply re-built from that customized value when `debbugs-gnu' is
started.
This didn't use to be a problem because stopping Gnus used to leave the
registry hanging around. I changed that in 2815174f as part of
preventing the registry from being loaded twice at startup, and I just
think it's good practice not to leave this (potentially huge) data
structure lingering after shutdown.
I can imagine a few possible solutions, but none of them are very
appealing. debbugs-gnu seems stuck somewhere between "too Gnus" and "not
Gnus enough".
Eric
next prev parent reply other threads:[~2019-09-15 0:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 7:11 bug#36903: 27.0.50; gnus registry vs. debbugs Michael Heerdegen
2019-08-03 15:38 ` Eric Abrahamsen
2019-08-03 23:47 ` Michael Heerdegen
2019-08-04 0:16 ` Eric Abrahamsen
2019-08-04 0:27 ` Eric Abrahamsen
2019-08-04 0:44 ` Noam Postavsky
2019-08-04 1:41 ` Eric Abrahamsen
2019-08-04 1:09 ` Michael Heerdegen
2019-08-04 2:10 ` Eric Abrahamsen
2019-08-04 2:35 ` Eric Abrahamsen
2019-08-07 17:59 ` Lars Ingebrigtsen
2019-08-07 20:22 ` Eric Abrahamsen
2019-08-11 23:34 ` Lars Ingebrigtsen
2019-08-12 15:24 ` Eric Abrahamsen
2019-09-14 15:04 ` Lars Ingebrigtsen
2019-09-15 0:27 ` Eric Abrahamsen [this message]
2019-09-15 12:20 ` Lars Ingebrigtsen
2019-09-15 23:31 ` Eric Abrahamsen
2019-09-16 13:24 ` Lars Ingebrigtsen
2019-09-16 22:37 ` Eric Abrahamsen
2019-09-19 17:39 ` Eric Abrahamsen
2019-09-21 8:40 ` Michael Albinus
2019-09-21 21:31 ` Eric Abrahamsen
2019-09-22 1:04 ` Michael Heerdegen
2019-09-22 2:36 ` Eric Abrahamsen
2019-09-22 8:02 ` Michael Albinus
2019-09-25 9:39 ` Michael Heerdegen
2019-09-25 16:30 ` Eric Abrahamsen
2019-10-01 23:27 ` Eric Abrahamsen
2019-10-02 12:36 ` Michael Albinus
2019-10-03 23:22 ` Eric Abrahamsen
2019-10-04 8:24 ` Michael Albinus
2019-10-04 16:59 ` Eric Abrahamsen
2019-10-05 7:53 ` Michael Albinus
2019-10-05 11:59 ` Eric Abrahamsen
2019-10-08 8:52 ` bug#37590: " Michael Heerdegen
2019-10-08 18:40 ` bug#36903: " Eric Abrahamsen
2019-10-09 14:37 ` Michael Heerdegen
2019-08-12 15:36 ` Eric Abrahamsen
2019-08-12 18:30 ` Lars Ingebrigtsen
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=87v9tuh08w.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36903@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).