On (May-10-16|14:39), Will Yardley wrote: > On Tue, May 10, 2016 at 01:10:00PM -0700, Yoshiki Vazquez-Baeza wrote: > > On (May-10-16|13:02), Will Yardley wrote: > > > 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 > > Well the 123 vs. 321 thing might be more due to what $sort_aux is set to > (i.e., whether sorting by received time / date header, or reverse). > > I'm not sure which Github emails you're seeing (and obviously Github is > only one example), but the examples I find from them (for both issue > tracking and pull requests) *are* threaded properly in Mutt (that is, > related messages are tied together; unrelated messages are not). > > For example, from a bug report / issue tracking request: > Message-ID: <someuser/somerepo/issues/731/211759...@github.com> > In-Reply-To: <someuser/somerepo/issues/7...@github.com> > > or from a pull request: > Message-ID: <foo/repo/pull/86/issue_event/656085...@github.com> > In-Reply-To: <foo/repo/pull/8...@github.com> > References: <foo/repo/pull/8...@github.com> > > The latter shows up like this for me in Mutt when threads are expanded: > > 4191 May 10 someone ( 51K) [foo/repo] Merging ..... > .... > 4192 May 10 someone ( 50K) `-> > 4193 May 10 someone ( 49K) `=> > 4194 May 10 someone ( 53K) [foo/repo2] Blah blah blah > 4195 May 10 someone ( 53K) |=> > 4196 May 10 someone ( 50K) `-> > > and like this when collapsed: > 4191 May 10 someone ( 51K) 3 [foo/repo] Merging ..... > .... > 4194 May 10 someone ( 53K) 3 [foo/repo2] Blah blah blah >
Thanks that's very helpful, I know what's going on now! You probably have: set sort = threads set sort_aux = last-date-received I have set sort = threads set sort_aux = reverse-last-date-received Which puts newest threads at the top of the index and in most properly formed threads, I can read email top-down i.e. I read an email and then hit next-entry (J) and start reading the next email. That's probably the same you do, even with GH emails. However mine are sorted the other way around, and because in GH no e-mail seems to be in response to any email, they are just grouped as part of the same message, like this (notice the timestamps): [-](May-10-16|22:43) |1.3K| Penguin McHelpe ┬>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:24) |1.3K| Penguin McHelpe ├>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:22) |1.3K| Penguin McHelpe ├>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:22) |1.3K| Penguin McHelpe ├>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:22) |1.3K| Penguin McHelpe └>Re: [ElDeveloper/data] test (#1 Whenever I follow a GH conversation, I have to start in the email at the bottom and go bottom->up, as opposed to top->down. Note that if these messages were in response to each other, they would look something like this (which is what most of my threads look like): [-](May-10-16|22:22) |1.3K| Penguin McHelpe ┬>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:22) |1.3K| Penguin McHelpe └>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:22) |1.3K| Penguin McHelpe └>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:24) |1.3K| Penguin McHelpe └>Re: [ElDeveloper/data] test (#1 [-](May-10-16|22:43) |1.3K| Penguin McHelpe └>Re: [ElDeveloper/data] test (#1 Anyways, thanks everyone! PS - I'm aware this is not a problem with mutt, this is just a *feature* of GH.
