From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: gnus-treat-date-lapsed + gnus-treat-date-user-defined
Date: Mon, 22 Aug 2005 21:46:31 +0900 [thread overview]
Message-ID: <b4md5o6dtqw.fsf@jpl.org> (raw)
In-Reply-To: <quack.20050819T0208.lthk6iiwayf@roar.cs.berkeley.edu>
>>>>> In <quack.20050819T0208.lthk6iiwayf@roar.cs.berkeley.edu> Karl Chen wrote:
> I use both `gnus-treat-date-user-defined' and
> `gnus-treat-date-lapsed', with `(setq
> gnus-article-date-lapsed-new-header t)'. This combination used to
> work, but recently something changed (I couldn't find anything
> relevant in cvs diffs or ChangeLog).
I did it, sorry. I was not aware those who use
`gnus-treat-date-user-defined' also use other date treatments.
Because it is possible to insert any date headers using
`gnus-article-time-format'. For example:
(setq gnus-treat-date-user-defined 'head
gnus-article-time-format
(lambda (time)
(let ((date (message-make-date time)))
(format "Date: %s\nX-Sent: %s"
(article-make-date-line date 'ut)
(article-make-date-line date 'lapsed)))))
(The code is inefficient, so it's no more than an example,
though.)
> The problem is `gnus-article-date-lapsed' is run after
> `gnus-treat-date-user', and `gnus-treat-date-user' deletes both
> the Date: and X-Sent: headers when writing the new Date: header.
> I imagine the date-{original,iso8601} have the same problem. The
> below patch fixes it by simply reordering them.
The patch seems good anyway, and I cannot imagine any obstacle
occurring with it. So, I'd like to install it, later.
> In the long term, a better solution would be:
> - `gnus-treat-date-lapsed' only adds X-Sent:; never deletes Date:
> - A new `gnus-treat-delete-date' deletes Date:
> - Un-combine the X-Sent: and Date: reformatting functions
I think it's worth to make a study of them. Thanks.
prev parent reply other threads:[~2005-08-22 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 9:08 Karl Chen
2005-08-22 12:46 ` Katsumi Yamaoka [this message]
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=b4md5o6dtqw.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).