From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Totally unrelated message shown in thread, sometimes
Date: Fri, 25 Dec 2020 21:58:19 -0800 [thread overview]
Message-ID: <87k0t5un0k.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87o8ihun76.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>> Eric writes:
>>
>>> A suggestion: I get strange behaviour whenever I have tried to use any
>>> of the daemons. Usually, hitting M-g on the group before entering it
>>> fixes things. Next time you see a strangely threaded summary buffer,
>>> leave with Q (gnus-summary-exit-no-update, not lower case q), hit M-g on
>>> the group, and enter it again. See if you get different threading and
>>> report here?
>>
>> This "two articles get mixed together"-thing just happened to me again.
>> It was just after my laptop had a network hiccup (losing connection to
>> the access point).
>>
>> More specifically, an article in a newsgroup,
>> nntp+fb:feedbase.blog.risks, showed it's own headers mixed with headers
>> from an article in my nndraft:delayed group. It looked spooky:
>>
>> · https://koldfront.dk/misc/gnus/mixup.png
>
> Spooky, indeed. Does this only ever happen with delayed articles, or
> with other draft articles, too? Was drafting and delaying the outgoing
> article the last thing you did before opening this group and seeing the
> fubar'ed headers? Or had you delayed it a while ago? And did you see the
> doubled headers on only one message in this group, or for every message?
I guess what I'm getting at with that last question is: is there any
chance that the article number of the delayed message in the delayed
group was the same as the article number of the article with doubled
headers in the feedbase group?
next prev parent reply other threads:[~2020-12-26 6:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 7:45 Pankaj Jangid
2020-11-25 9:21 ` Adam Sjøgren
2020-11-25 10:08 ` Pankaj Jangid
2020-11-25 17:07 ` Eric Abrahamsen
2020-11-25 17:32 ` Adam Sjøgren
2020-11-25 17:40 ` Eric Abrahamsen
[not found] ` <87d001nenj.fsf@ust.hk>
[not found] ` <87k0u8zdv8.fsf@tullinup.koldfront.dk>
[not found] ` <87pn3zkfos.fsf@ucl.ac.uk>
2020-12-25 23:40 ` Adam Sjøgren
2020-12-26 5:54 ` Eric Abrahamsen
2020-12-26 5:58 ` Eric Abrahamsen [this message]
2020-12-26 14:20 ` Adam Sjøgren
2020-12-26 19:30 ` Eric Abrahamsen
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=87k0t5un0k.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@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.
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 NNTP newsgroup(s).