From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] joining threads manually
Date: Tue, 13 Nov 2007 09:12:54 -0800 [thread overview]
Message-ID: <1194973525-sup-1660@south> (raw)
In-Reply-To: <1194966571-sup-6200@timmy>
Excerpts from Eyal Oren's message of Tue Nov 13 07:12:44 -0800 2007:
> Due to other people's broken email clients, threads are sometimes not
> properly connected (eg. their client doesn't use the in-reply-to
> header). Mutt allows you to manually join such broken threads by
> first tagging the child message and then going to the parent message
> and pressing '&'.
There is an option in config.yaml to also thread by subject, although I
haven't tested it for quite a while. But that has its own problems, so I
leave it off by default. The best solution, of course, is to go to where
those people live and punish them until they switch to a reasonable
email client.
> Would it be possible to do this in sup? Given a pointer to some places
> in the code, I could try to hack something.
Here's what I would try. In thread-index-mode, given n>1 tagged threads,
you simply want to add the message-id of the root message of the
earliest thread to the refs field of the root messages of all other
threads. (You'll have to make refs a r/w attribute of message instead of
r/o.) That will thread them all at the top level, which probably is the
most reasonable thing to do.
Then you'll need to update thread-index-mode's Threadset to handle the
new structure. It might be enough to call ThreadSet#link (which you'll
have to make public). Or you can first delete the messages from the
threadset with #remove, munge the refs as above, and re-add them with
#add_message. This step will require a little experimentation.
Once the threadset's in place, you can call the ThreadIndexMode#update
to regenerate the display.
> PS: Mutt also allows you to break threads ('#') but for me that's less
> useful.
If you can accomplish the above, then this will be very similar,
although it will belong in thread-view-mode.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-11-13 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 15:12 Eyal Oren
2007-11-13 16:42 ` Michael Gurski
2007-11-13 17:12 ` William Morgan [this message]
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=1194973525-sup-1660@south \
--to=wmorgan-sup@masanjin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox