Re: It's still 2020. :-(
On Mon, Jan 04, 2021 at 01:51:45PM +, Alan wrote in : In that case, happy new year David! (and everyone else) Ehr Alan too!
Re: It's still 2020. :-(
On Mon, Jan 04, 2021 at 01:51:45PM +, Alan wrote in
:
Perhaps check for a custom display format?
Indeed, that is my problem! My index_format is defined by:
set index_format = "%4C %Z %{%e %b %G} %-15.15L (%4l / %4c) %s"
^
, and that %G means "ISO 8601 week-based year". What I need is %Y. All
from the man page for strftime. I haven't tried it yet, but I'm certain
this change will bring me back the real year for 2021-01-01 -> ...-03.
In that case, happy new year David! (and everyone else)
Re: It's still 2020. :-(
Hello, David
On Mon, Jan 04, 2021 at 08:13:59 -0500, David Haguenauer wrote:
> Hi Alan,
> * Alan Mackenzie , 2021-01-04 12:59:34 Mon:
> > I'm now seeing dates from 4 January as 2021, those of 3 January and
> > before as 2020. It is almost as though some piece of software thinks the
> > year begins on 4th Jan, not 1st Jan.
> > Here's a short section of my inbox, with mails from various time zones
> > straddling midnight:
> > 164997 Os3 Jan 2020 Michael ( 92 / 3.5K) └─>
> > 164998 N 4 Jan 2021 Dr Rainer Woito ( 45 / 1.4K) └─>
> It looks almost as if you have a date display format that uses the
> year from the Posix week, instead of the year from the day.
> Indeed, week 53 of 2020 ended on Jan 3; today, Jan 4, starts week 1 of
> 2021.
> Perhaps check for a custom display format?
Indeed, that is my problem! My index_format is defined by:
set index_format = "%4C %Z %{%e %b %G} %-15.15L (%4l / %4c) %s"
^
, and that %G means "ISO 8601 week-based year". What I need is %Y. All
from the man page for strftime. I haven't tried it yet, but I'm certain
this change will bring me back the real year for 2021-01-01 -> ...-03.
Thank you indeed!
> --
> David Haguenauer
--
Alan Mackenzie (Nuremberg, Germany).
Re: It's still 2020. :-(
Hi Alan, * Alan Mackenzie , 2021-01-04 12:59:34 Mon: > I'm now seeing dates from 4 January as 2021, those of 3 January and > before as 2020. It is almost as though some piece of software thinks the > year begins on 4th Jan, not 1st Jan. > > Here's a short section of my inbox, with mails from various time zones > straddling midnight: > > 164997 Os3 Jan 2020 Michael ( 92 / 3.5K) └─> > 164998 N 4 Jan 2021 Dr Rainer Woito ( 45 / 1.4K) └─> It looks almost as if you have a date display format that uses the year from the Posix week, instead of the year from the day. Indeed, week 53 of 2020 ended on Jan 3; today, Jan 4, starts week 1 of 2021. Perhaps check for a custom display format? -- David Haguenauer signature.asc Description: PGP signature
Re: It's still 2020. :-(
Hello, Remco. On Mon, Jan 04, 2021 at 06:23:28 -0500, Remco Rijnders wrote: > On Mon, Jan 04, 2021 at 11:17:05AM +, Alan wrote in > : > >I've just had a look at my (mbox) spool file with > >$ tail -n5000 Mail/spool | less > >. The dates I see there are 2021. > >Maybe this has been fixed in 2.0.3. I'll wait for Gentoo's release > >cycle to catch up with 2.0.3/4. > For what it is worth, I can't think of a single reason or recent change why > mutt > would display such a thing. Can you give an example of any such entry that you > are seeing? I'm now seeing dates from 4 January as 2021, those of 3 January and before as 2020. It is almost as though some piece of software thinks the year begins on 4th Jan, not 1st Jan. Here's a short section of my inbox, with mails from various time zones straddling midnight: 164997 Os3 Jan 2020 Michael ( 92 / 3.5K) └─> 164998 N 4 Jan 2021 Dr Rainer Woito ( 45 / 1.4K) └─> 164999 Ns4 Jan 2021 Michael ( 72 / 2.9K) └─> 165000 O 3 Jan 2020 Daniel Martín ( 110 / 4.3K) [PATCH] Fix some failing tests in BSD systems 165001 O 3 Jan 2020 Eli Zaretskii ( 21 / 0.9K) ├─> 165002 N 3 Jan 2020 Daniel Martín ( 94 / 3.9K) │ ├─> 165003 N 4 Jan 2021 Dmitry Gutov( 11 / 0.4K) │ └─> 165004 N 4 Jan 2021 Eli Zaretskii ( 21 / 0.8K) │ └─> 165005 N 4 Jan 2021 Dmitry Gutov( 49 / 1.8K) └─> 165006 N 3 Jan 2020 Stefan Monnier ( 11 / 0.3K) └─> 165007 O 3 Jan 2020 Glenn Morris( 9 / 0.2K) Re: master 64f2c96 2/2: Make a process test faster. 165008 N + 3 Jan 2020 MAILER-DAEMON@m ( 48 / 1.7K) failure notice 165009 N 3 Jan 2020 Sheena Thomas (12850 / 963K) Happy New Year 165010 N 4 Jan 2021 Basil L. Contov ( 46 / 1.1K) Re: master d3d60ab: Remove unnecessary dependency on seq library 165011 N 3 Jan 2020 Mark Oteiza ( 21 / 0.5K) └─> 165012 N 4 Jan 2021 Bertram Scharpf ( 45 / 1.6K) [gentoo-user] Yet another USE flag problem 165013 N 4 Jan 2021 Arve Barsnes( 9 / 0.3K) └─> > The only thing that comes to my mind right now is maybe you have a > format set that cuts the date displayed short, so that Jan 2021 gets > displayed as "Jan 20" and you didn't notice it before as that would > have been correct in the past year. Thanks for the suggestion, but my year display is of all 4 digits (a Y2K problem veteran :-). > I don't think mutt 2.0.3/4 will make a difference for you here. I admit I'm mystified as to what exactly could be causing this. > Kind regards, > Remco -- Alan Mackenzie (Nuremberg, Germany).
Re: It's still 2020. :-(
On Mon, Jan 04, 2021 at 11:17:05AM +, Alan wrote in : I've just had a look at my (mbox) spool file with $ tail -n5000 Mail/spool | less . The dates I see there are 2021. Maybe this has been fixed in 2.0.3. I'll wait for Gentoo's release cycle to catch up with 2.0.3/4. For what it is worth, I can't think of a single reason or recent change why mutt would display such a thing. Can you give an example of any such entry that you are seeing? The only thing that comes to my mind right now is maybe you have a format set that cuts the date displayed short, so that Jan 2021 gets displayed as "Jan 20" and you didn't notice it before as that would have been correct in the past year. I don't think mutt 2.0.3/4 will make a difference for you here. Kind regards, Remco
Re: It's still 2020. :-(
Hello, Anders. On Mon, Jan 04, 2021 at 11:39:17 +0100, Anders Damsgaard wrote: > Hi Alan, > * Alan Mackenzie [2021-01-04 10:18:36 +]: > >I'm using mutt 2.0.2 (from Gentoo). > >On mutt's list of incoming mails (my inbox), it displays the date of all > >new mails as January 2020, even though the date header displayed in each > >individual mail is correctly January 2021. > >If this has already been fixed in 2.0.3 or 2.0.4, then sorry for the > >noise. > No problem here with 2.0.3. Are you sure this is not related to > the mail server? If you sync the files to a local maildir, you can > check the header in one of the plaintext mail files. I've just had a look at my (mbox) spool file with $ tail -n5000 Mail/spool | less . The dates I see there are 2021. Maybe this has been fixed in 2.0.3. I'll wait for Gentoo's release cycle to catch up with 2.0.3/4. Thanks for the reply! > Anders > -- > Anders Damsgaard > https://adamsgaard.dk > gopher://adamsgaard.dk -- Alan Mackenzie (Nuremberg, Germany).
Re: It's still 2020. :-(
Hi Alan, * Alan Mackenzie [2021-01-04 10:18:36 +]: Hello, mutt. I'm using mutt 2.0.2 (from Gentoo). On mutt's list of incoming mails (my inbox), it displays the date of all new mails as January 2020, even though the date header displayed in each individual mail is correctly January 2021. If this has already been fixed in 2.0.3 or 2.0.4, then sorry for the noise. No problem here with 2.0.3. Are you sure this is not related to the mail server? If you sync the files to a local maildir, you can check the header in one of the plaintext mail files. Anders -- Anders Damsgaard https://adamsgaard.dk gopher://adamsgaard.dk
It's still 2020. :-(
Hello, mutt. I'm using mutt 2.0.2 (from Gentoo). On mutt's list of incoming mails (my inbox), it displays the date of all new mails as January 2020, even though the date header displayed in each individual mail is correctly January 2021. If this has already been fixed in 2.0.3 or 2.0.4, then sorry for the noise. -- Alan Mackenzie (Nuremberg, Germany).
