From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 36903@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#36903: 27.0.50; gnus registry vs. debbugs
Date: Sat, 21 Sep 2019 19:36:43 -0700 [thread overview]
Message-ID: <87v9tl9hvo.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r249jg44.fsf@web.de> (Michael Heerdegen's message of "Sun, 22 Sep 2019 03:04:43 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Yeah, I was too hasty with this whole thing. The backtrace you posted
>> seems to be unrelated to the registry issue I was trying to fix (at
>> least, I can't immediately see how it could arise from that),
>
> FWIW, your fix works for me.
>
>> but I'll see if I can reproduce.
>
> I can't, but I can if I do
>
> (with-eval-after-load 'gnus
> (add-hook 'gnus-select-group-hook #'gnus-group-set-timestamp))
Okay, this is a completely different bug, coincidentally also caused by
changes I put in! The end of `gnus-group-set-info' tries to manipulate
`gnus-newsrc-alist', which is nil in the case of debbugs-gnu.
This all resulted from me trying to turn groups into objects, instead of
lists. If they were objects, we could edit them without having to worry
about breaking references to them. I can wrap this chunk of code in a
test to see if `gnus-newsrc-alist' is a list, but... I just wish groups
could be objects.
next prev parent reply other threads:[~2019-09-22 2:36 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
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 [this message]
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=87v9tl9hvo.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36903@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
/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).