On (May-10-16|13:02), Will Yardley wrote: > On Tue, May 10, 2016 at 12:06:35PM -0700, Yoshiki Vazquez-Baeza wrote: > > On (May-10-16|10:51), Will Yardley wrote: > > > On Sat, May 07, 2016 at 10:11:57PM -0700, Thomas Roessler wrote: > > > > If I think about the single most critical feature that makes today's > > > > mail volume manageable for me (other than priority inbox), then it's > > > > conversation view: The ability to page through an entire mail thread > > > > quickly without having to go back to the index view, and without > > > > having to think about having to move to another message. > > > > > > If you collapse threads, isn't this possible? > > > > This is what I do myself, I always have threads collapsed and the index > > is "thread sorted", however I have to say that not all services from > > which I receive email thread the messages properly, most notably GitHub > > will not thread messages and instead messages are sorted in the order > > they come, not in the order they really should have. I even emailed > > their team a while ago, and they explained this is not something they > > could change :( If I'm understanding correctly, this sort of problem > > would be fixed with a "conversation view", so I would find this feature > > very useful as well! > > I think "conversations" in Gmail are essentially the same thing as > threads, no?
As you mention, this depends on the settings you have. However if I understand correctly, the structure of a thread is determined by the in-reply-to header attribute. GitHub does not include this attrribute in the emails they send you, so all your emails are piled in a single thread but with no thread structure on their own, as far as I know, there's no way to fix this. Gmail on the other hand will just order these as you expect: Message 1 Message 2 Message 3 Mutt will do this: Message 3 Message 2 Message 1 Suggestions on how to cope with this are greatly appreciated :)
