* p0.88 (and since time immemorial?) date-lapsed error
@ 1999-06-18 1:42 Karl Kleinpaste
1999-07-03 10:31 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Karl Kleinpaste @ 1999-06-18 1:42 UTC (permalink / raw)
With gnus-treat-date-lapsed set to 'head, received and Gcc'd forwarded
messages display such that *both* Date: headers are replaced with the
same X-Sent header.
The embedded Date: header ought to be preserved. Or at the least, its
lapse ought to be calculated separately.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: p0.88 (and since time immemorial?) date-lapsed error
1999-06-18 1:42 p0.88 (and since time immemorial?) date-lapsed error Karl Kleinpaste
@ 1999-07-03 10:31 ` Lars Magne Ingebrigtsen
1999-07-04 15:37 ` Karl Kleinpaste
0 siblings, 1 reply; 4+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-07-03 10:31 UTC (permalink / raw)
Karl Kleinpaste <karl@justresearch.com> writes:
> With gnus-treat-date-lapsed set to 'head, received and Gcc'd forwarded
> messages display such that *both* Date: headers are replaced with the
> same X-Sent header.
I'm not sure I follow you here, but
`gnus-article-date-lapsed-new-header' controls whether the Date header
is removed when looking at the lapsed header.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: p0.88 (and since time immemorial?) date-lapsed error
1999-07-03 10:31 ` Lars Magne Ingebrigtsen
@ 1999-07-04 15:37 ` Karl Kleinpaste
1999-07-05 3:58 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Karl Kleinpaste @ 1999-07-04 15:37 UTC (permalink / raw)
Karl Kleinpaste <karl@justresearch.com> writes:
>> With gnus-treat-date-lapsed set to 'head, received and Gcc'd forwarded
>> messages display such that *both* Date: headers are replaced with the
>> same X-Sent header.
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I'm not sure I follow you here, but
> `gnus-article-date-lapsed-new-header' controls whether the Date header
> is removed when looking at the lapsed header.
No, that's not what I meant.
When one forwards a message, both the new, enclosing message and the
contained message have Date: headers. Setting gnus-treat-date-lapsed
results in displays of this flavor:
________________
From: Karl Kleinpaste <karl@justresearch.com>
Subject: [Karl Kleinpaste <karl@justresearch.com>] test
To: karl@beaver.jprc.com
»»--> X-Sent: 1 week, 4 days, 18 hours, 20 minutes, 43 seconds ago
[1. text/plain]
enclosing text.
[2. message/rfc822]
From: Karl Kleinpaste <karl@justresearch.com>
Subject: test
To: karl@beaver.jprc.com
»»--> X-Sent: 1 week, 4 days, 18 hours, 20 minutes, 43 seconds ago
inner text.
________________
The X-Sent: are identical, but in the original message file, they are:
Date: 22 Jun 1999 17:00:38 -0400
Date: 22 Jun 1999 16:49:59 -0400
The 2nd is not treated individually; the 1st is given "lapsed"
treatment, and that string is substituted for all Date: headers.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: p0.88 (and since time immemorial?) date-lapsed error
1999-07-04 15:37 ` Karl Kleinpaste
@ 1999-07-05 3:58 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 4+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-07-05 3:58 UTC (permalink / raw)
Karl Kleinpaste <karl@justresearch.com> writes:
> When one forwards a message, both the new, enclosing message and the
> contained message have Date: headers.
Yup. Fix in Pterodactyl Gnus v0.92.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-07-05 3:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-06-18 1:42 p0.88 (and since time immemorial?) date-lapsed error Karl Kleinpaste
1999-07-03 10:31 ` Lars Magne Ingebrigtsen
1999-07-04 15:37 ` Karl Kleinpaste
1999-07-05 3:58 ` Lars Magne Ingebrigtsen
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).