From: Kevin Shell <kshell@gmx.com>
To: ding@gnus.org
Subject: Re: Gnus wrong message threading
Date: Sun, 20 Sep 2020 19:31:51 +0800 [thread overview]
Message-ID: <87pn6g1y6w.fsf@fedora.osfans.org> (raw)
In-Reply-To: <87363cogub.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Kevin writes:
>
>>> Where would you have expected them to be linked, when all that connects
>>> them is the Subject, as they have no In-Reply-To/References?
>
>> How about linked to root message with special marks characters
>
> They are linked to the root message. Isn't the [] vs <> showing that
> they are special?
>
I view with trn-style threads with %B mentioned in my previous mail,
no [] and <> characters.
>> and add two commands/functions like link-threads break-thread and let
>> the user joining the two threads together.
>
> Aren't those commands there already:
>
> · https://www.gnus.org/manual/gnus_39.html#Thread-Commands
>
> ?
>
Found gnus-summary-reparent-thread and gnus-summary-reparent-children
equivalent to link-threads. :-)
But still no break-thread equivalent commands.
>>>> They are web mailers that don't generate In-Reply-To and References
>>>> headers.
>
>>> Really? I'm quite sure that both Gmail and GMX generate In-Reply-To and
>>> Reference headers when you reply to an email.
>>>
>>> If Gmail didn't there would have been an uproar.
>>>
>>> You are right that those two emails do not have In-Reply-To and
>>> Reference headers, but emails from Gmail and GMX usually do.
>>
>> They are mails back in year *2012*.
>
> What is your point?
>
I mean they were old MUAs back in *2012* that don't generate the two headers.
--
kevin
next prev parent reply other threads:[~2020-09-20 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 2:15 Kevin Shell
2020-09-19 11:23 ` Adam Sjøgren
2020-09-19 13:56 ` Kevin Shell
2020-09-19 14:08 ` Adam Sjøgren
2020-09-20 2:33 ` Kevin Shell
2020-09-20 9:51 ` Adam Sjøgren
2020-09-20 10:33 ` Kevin Shell
2020-09-20 10:58 ` Adam Sjøgren
2020-09-20 11:31 ` Kevin Shell [this message]
2020-09-20 12:17 ` Adam Sjøgren
2020-09-19 14:14 ` 황병희
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=87pn6g1y6w.fsf@fedora.osfans.org \
--to=kshell@gmx.com \
--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).