From: Philipp Haselwarter <philipp.haselwarter@gmx.de>
To: ding@gnus.org
Subject: Re: Date header rewrite
Date: Tue, 01 Feb 2011 19:23:10 +0100 [thread overview]
Message-ID: <877hdjr4vl.fsf@nzebook.haselwarter.org> (raw)
In-Reply-To: <smuzkqh41zq.fsf@linuxpal.mit.edu>
Greg Troxel <gdt@work.lexort.com> writes:
> As I hinted earlier, I've now totally rewritten the way date headers are
> customised. You can now have as many Date headers as you like.
>
> This isn't clearly a bug, but I think it is. In the "ago" display,
> seconds are omitted if 0. This results in something like
>
> Date: Sun, 30 Jan 2011 17:56:53 -0800 (11 hours, 49 minutes, 59 seconds ago)
> Date: Sun, 30 Jan 2011 17:56:53 -0800 (11 hours, 50 minutes ago)
> Date: Sun, 30 Jan 2011 17:56:53 -0800 (11 hours, 50 minutes, 1 second ago)
>
> I find the seconds coming and going to be distracting. Plus I wonder
> if the minutes would go away as well when 0.
>
>
> I have no problem omitting leading hours/days/minutes as zero, and
> omitting seconds because there is a day, etc. I am only objecting to
> suppressing fields because they are zero.
>
+1
I'd also prefer if the seconds/the least relevant portion didn't
disappear when it's zero; a counter is fine with me, but the changing
length of the date string is somewhat distracting.
Oh and what happened to months (between weeks and years)?
--
Philipp Haselwarter
next prev parent reply other threads:[~2011-02-01 18:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 1:56 Lars Ingebrigtsen
2011-01-31 8:07 ` Francis Moreau
2011-01-31 9:38 ` Rupert Swarbrick
2011-01-31 10:34 ` Robert Pluim
2011-01-31 10:43 ` Lars Ingebrigtsen
2011-01-31 11:30 ` Robert Pluim
2011-02-01 1:55 ` Lars Ingebrigtsen
2011-02-01 7:42 ` Robert Pluim
2011-02-01 19:23 ` Eric S Fraga
2011-02-03 4:14 ` Lars Ingebrigtsen
2011-01-31 13:49 ` Greg Troxel
2011-02-01 1:07 ` Lars Ingebrigtsen
2011-02-01 1:47 ` Richard Riley
2011-02-01 2:04 ` Lars Ingebrigtsen
2011-02-01 2:25 ` Richard Riley
2011-02-01 2:38 ` Lars Ingebrigtsen
2011-02-01 2:44 ` Richard Riley
2011-02-01 3:10 ` Lars Ingebrigtsen
2011-02-01 6:41 ` Richard Riley
2011-02-01 18:23 ` Philipp Haselwarter [this message]
2011-02-01 6:05 ` Michael Welsh Duggan
2011-02-01 6:14 ` Lars Ingebrigtsen
2011-02-01 17:05 ` James Cloos
2011-02-02 11:18 ` Francis Moreau
2011-02-01 18:54 ` Greg Troxel
2011-02-03 4:13 ` Lars Ingebrigtsen
2011-02-03 11:50 ` Greg Troxel
2011-02-01 8:11 ` Francis Moreau
2011-02-01 8:23 ` Robert Pluim
2011-02-01 9:17 ` Francis Moreau
2011-02-01 10:06 ` Tassilo Horn
2011-02-01 10:11 ` Francis Moreau
2011-02-01 10:19 ` Lars Ingebrigtsen
2011-02-01 10:08 ` Lars Ingebrigtsen
2011-02-01 10:11 ` Francis Moreau
2011-02-01 10:08 ` Robert Pluim
2011-02-01 10:09 ` Lars Ingebrigtsen
2011-02-01 11:15 ` Robert Pluim
2011-02-03 4:10 ` Lars 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=877hdjr4vl.fsf@nzebook.haselwarter.org \
--to=philipp.haselwarter@gmx.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).