From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: Date timer in Gnus article buffers
Date: Mon, 27 Jun 2011 19:04:31 +0200 [thread overview]
Message-ID: <87ei2fmcio.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <87wrg7z294.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 27 Jun 2011 12:07:51 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Does the Date: field in the article buffer really need to show the time
> elapsed down to the number of seconds?
> [...]
> I'd suggest suppressing the number of seconds---at the very least if
> more than one minute has elapsed.
Is it so distracting to see the seconds? The problem I'm seeing with the
Date: header is that it shows the date as set by the sender of the
message. When someone has their date/time set incorrectly, like 5 hours
in the future, and when sorting the summary by date, this screws up the
sorting order.
An alternative is to sort by Received: headers --- mutt does something
like that very nicely. I don't know exactly how mutt does it. A rule
like "if the Date: header has a date that's in the future, use the
Received: header for sorting and in the summary view" would be useful.
Perhaps it's possible to make gnus insert the date from the Received:
header as an additional header and use that for sorting and for
displaying the headers of a message instead (or in addition to) the
Date: header. I'd call such a header X-Gnus-Rdate:.
If you were to use such a X-Gnus-Rdate: header, you could make it so
that it doesn't show the seconds if you don't want to see them :)
Personally, I don't care much about the Date: header because I have no
way of knowing if the date was set correctly, so I'd use the
X-Gnus-Rdate: header instead. I wish I knew gnus well enough to make it
so ...
next prev parent reply other threads:[~2011-06-27 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:07 Chong Yidong
2011-06-27 17:04 ` lee [this message]
2011-06-30 2:22 ` Lars Magne Ingebrigtsen
2011-06-30 7:01 ` Tassilo Horn
2011-06-30 7:38 ` Peter Münster
2011-06-30 8:04 ` Julien Danjou
2011-06-30 17:04 ` Lars Magne Ingebrigtsen
2011-06-30 18:51 ` Julien Danjou
2011-06-30 20:53 ` Peter Münster
2011-06-30 21:47 ` Lars Magne Ingebrigtsen
2011-06-30 22:15 ` Julien Danjou
2011-06-30 22:30 ` Lars Magne Ingebrigtsen
2011-07-01 9:01 ` Julien Danjou
2011-07-01 10:01 ` Lars Magne Ingebrigtsen
2011-07-01 10:08 ` Julien Danjou
2011-07-01 10:18 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ei2fmcio.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).