From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: [patch] age depending date-format
Date: Tue, 16 Oct 2001 16:52:18 -0400 [thread overview]
Message-ID: <2n1yk3tiil.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <wv1vmkvy.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Tue, 16 Oct 2001 21:42:57 +0200")
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> Hi
>
> I did some more testing and error handling on my code I posted in
> <archive.pu7pc20r.fsf@hschmi22.userfqdn.rz-online.de>.
>
> It should work without problems. What it does is the following:
> Add a new item (%q) to gnus-summary-line-format-alist which calls
> gnus-user-date(date-header).
>
> gnus-user-date formats the date accordingly to
> gnus-user-date-day
> gnus-user-date-week
> gnus-user-date-old
>
> That means that if the message is of today you get e.g. 10:24
> if not older than 7 days you Mon 12:35
> and if it's older you Okt 16
>
> gnus-user-* can hold any valid value for format-time-string.
It is cute, but we'd better let users use %uX instead of adding %q
into g-s-l-f-a. For example, (defalias 'gnus-user-format-function-X
'gnus-user-date).
A suggestion. Is it better to use a variable like
gnus-user-data-format-alist instead of gnus-user-date-format-day and
it friends? g-u-d-f-a is a list of cons of elapsed time (or symbol)
and format. For example,
(defvar gnus-user-data-format-alist
'((day-in-seconds . "%k:%M")
(604800 . "%a %k:%M")
(t . "%d.%m))
"Blah blah")
ShengHuo
next prev parent reply other threads:[~2001-10-16 20:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 19:42 Frank Schmitt
2001-10-16 20:52 ` ShengHuo ZHU [this message]
2001-10-17 7:16 ` Frank Schmitt
2001-10-17 16:09 ` ShengHuo ZHU
2001-10-17 16:34 ` Frank Schmitt
2001-10-17 11:50 ` Kai Großjohann
2001-10-17 13:59 ` ShengHuo ZHU
2001-10-17 14:08 ` Didier Verna
2001-10-17 14:11 ` Colin Marquardt
2001-10-17 14:36 ` Didier Verna
2001-10-17 15:05 ` Kai Großjohann
2001-10-17 15:33 ` Didier Verna
2001-10-17 15:30 ` Paul Jarc
2001-10-17 15:41 ` Didier Verna
2001-10-17 16:14 ` Per Abrahamsen
2001-10-17 16:19 ` Paul Jarc
2001-10-17 16:37 ` Simon Josefsson
2001-10-17 16:52 ` Kai Großjohann
2001-10-17 17:03 ` Paul Jarc
2001-10-17 18:11 ` Per Abrahamsen
2001-10-17 18:08 ` Per Abrahamsen
2001-10-17 16:20 ` Amos Gouaux
2001-10-17 16:51 ` Kai Großjohann
2001-10-18 6:44 ` Yair Friedman (Jerusalem)
2001-10-17 15:09 ` Per Abrahamsen
2001-10-17 15:15 ` Per Abrahamsen
2001-10-17 15:19 ` Kai Großjohann
2001-10-17 16:04 ` ShengHuo ZHU
2001-10-17 20:35 ` Update of gnus-user-date (was: [patch] age depending date-format) Frank Schmitt
2001-10-17 21:34 ` ShengHuo ZHU
2001-10-18 7:53 ` Update of gnus-user-date Frank Schmitt
2001-10-18 10:08 ` Kai Großjohann
2001-10-19 17:11 ` Update of gnus-user-date (was: [patch] age depending date-format) Wes Hardaker
2001-10-17 10:51 ` [patch] age depending date-format Frank Schmitt
2001-10-17 15:05 ` Yair Friedman (Jerusalem)
2001-10-17 16:09 ` Frank Schmitt
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=2n1yk3tiil.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).