On Fri,May 23 11:37:AM, Cameron Simpson wrote: > >>I have no idea if it is normal. Besides, that should be irrelevant. Does it > >>work for you? If so, why? When not, why not? > > > >>> > >>> Sat,May 17 12:19:PM Karl Voit Writing a wrapper for the > >>> editor: mutt aborts in-between > >>> Sat,May 17 02:51:PM Kevin J. McCarthy ├─> > >>> Sun,May 18 04:14:AM Chris Green │ └─> > >>> Sat,May 17 05:04:PM Mike Glover └─> > >>> Sat,May 17 05:59:PM Karl Voit └─> > >>> Sat,May 17 09:51:PM Cameron Simpson ├─> > >>> Sun,May 18 02:58:AM Karl Voit │ └─> > >>> Sat,May 17 07:02:PM Gary Johnson └─> > > Ok, question 1: do you use %d or %D for the date field in your $index_format > string? [..] > Importantly, %D is the message date in your local time zone. If > you use %d, you get the sender's time zone (i.e., as it is in the message > header), and that will vary widely. Quite possibly producing the listing > above.
my index_format: set index_format="%?M?>& ?%2Z %15D %-20.20F %s" > Here is the same thread in my mail folder (with some stuff removed after the > ">") to make the lines fit. > > 18May2014 18:14 list mail - ┌> > 18May2014 04:51 Kevin J. McCart - ┌> > 18May2014 16:58 Karl Voit - │ ┌> > 18May2014 11:51 To Karl Voit - │ ┌> > 18May2014 09:02 Gary Johnson - │ ├> > 18May2014 07:59 Karl Voit - │┌> > 18May2014 07:04 Mike Glover - ├> > 18May2014 02:19 Karl Voit - Writing a wrapper for the editor: mutt > aborts in-between > > Notice that all the dates within a given subthread ore in order? This makes > me think you do not have an ordering problem but a display problem. That, pretty much, is what I'm trying to get to, only reversed, with the newest message, on the bottom. I wonder if other parts of my .muttrc breaking it. -- Guy Gold MERL Computer Services g...@merl.com
