~sircmpwn/aerc2#94
Add option for organizing messages into threads

Status
REPORTED
Submitter
~sircmpwn
Assigned to
No-one
Submitted
9 months ago
Updated
24 days ago
Labels
feature imap

~dxu 6 months ago

+1

This could be quite nice for following along on a long mailing list discussion.

~jeffas 5 months ago

https://github.com/emersion/go-imap-sortthread now has support for threading so this could make some progress.

I'm not entirely sure how the design for threading inside the client would work, config option / command / something else?

~labrat 5 months ago

A config option, you'll want to be able to set that to the default upon startup.

Commands aren't good for that

~dxu 5 months ago

I could see some use in being able to flip between date-sorted and thread-sorted. For example you just want to see the latest messages and then use a command to see the previous messages in the thread. That's sort of like how gmail works.

I certainly would not object to just having a config option as a first pass.

~labrat 5 months ago

You can always flip config options at runtime

set .

~labrat 5 months ago

... thanks sr.ht for stripping html that isn't even HTML for God's sake!

set category.option value

~keur 4 months ago

Just FYI, I have been working on this. Please ping me on IRC if you want to chat about it.

~flokli 24 days ago

I'd also be very interested in a threaded view. However, I don't think assembling threads should be done client-side.

IMAP seems to support threading, and backends like notmuch are also probably much faster when loading threads or displaying query results in threaded view.

~labrat 24 days ago

what gave you the notion that this will be implemented client side?

The patches sent by keur do use the workers ability to efficiently get the threads iirc

~flokli 24 days ago

You're right - found https://lists.sr.ht/~sircmpwn/aerc/patches/8864 now aswell, it indeed uses the workers for threading. I'll give it a try, and will also take a look at adding notmuch support :-)

~keur 24 days ago

You will still need some form of client side threading because not all IMAP servers support the extension. Notably Gmail has a nonstandard threading extension. Implementing REFERENCES client side and falling back on it if the thread extension is not supported ensures we support all servers. This is what mutt does (it doesn’t even utilize the extensions).

In v2 made the mistake of trying to do both server and client side threading in the same patch set. Instead I should’ve just cleaned up server side threading, got that reviewed and merged, then implemented client side threading.

On Feb 1, 2020, at 3:33 PM, ~flokli outgoing@sr.ht wrote:

I'd also be very interested in a threaded view. However, I don't think assembling threads should be done client-side.

IMAP seems to support threading, and backends like notmuch are also probably much faster when loading threads or displaying query results in threaded view.

View on the web: https://todo.sr.ht/~sircmpwn/aerc2/94#comment-5980

~keur referenced this from #94 24 days ago

Register here or Log in to comment, or comment via email.