From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: Date header rewrite
Date: Tue, 01 Feb 2011 11:08:48 +0100 [thread overview]
Message-ID: <pknsjw8ukwf.fsf@this.is.really.invalid> (raw)
In-Reply-To: <m2k4hkp10y.fsf@gmail.com>
Francis Moreau <francis.moro@gmail.com> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> Francis Moreau <francis.moro@gmail.com> writes:
>>
>>> Lars Ingebrigtsen <larsi@gnus.org> 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.
>>>>
>>>> I've removed a slew of date customisation variables, but it should still
>>>> respect the legacy variables. (Sort of.)
>>>
>>> With latest git as of this writing (head is at
>>> dd811978420ac00e1e71c00b9291aa667950afbf)
>>>
>>>
>>> This doing this doesn't work:
>>>
>>> (setq gnus-article-date-headers 'combined-elapsed)
>>> (setq gnus-article-update-date-headers nil)
>>>
>>> => article-make-date-line: Unknown conversion type: combined-elapsed
>>
>> It's 'combined-lapsed' (no e)
>>
>
> That's not what I'm seeing in the doc and changing it still fails:
>
> => article-make-date-line: Unknown conversion type: combine-lapsed
You've dropped the 'd' this time :)
Looks like the info docs are wrong. Doc in the code say:
`gnus-article-date-headers' is a variable declared in Lisp.
-- loaded from "gnus-art"
Value: (local lapsed)
Documentation:
A list of Date header formats to display.
Valid formats are `ut' (universal time), `local' (local time
zone), `english' (readable English), `lapsed' (elapsed time),
`combined-lapsed' (both the original date and the elapsed time),
`original' (the original date header), `iso8601' (ISO8601
format), and `user-defined' (a user-defined format defined by the
`gnus-article-time-format' variable).
You have as many date headers as you want in the article buffer.
Some of these headers are updated automatically. See
`gnus-article-update-date-headers' for details.
Robert
next prev parent reply other threads:[~2011-02-01 10:08 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
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 [this message]
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=pknsjw8ukwf.fsf@this.is.really.invalid \
--to=rpluim@gmail.com \
--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).