From: Didier Verna <verna@inf.enst.fr>
Cc: ding@gnus.org
Subject: Re: X-Sent
Date: 26 Jul 1999 18:46:46 +0200 [thread overview]
Message-ID: <qyjyag31hqh.fsf@metheny.enst.fr> (raw)
In-Reply-To: Shaun Lipscombe's message of "26 Jul 1999 17:25:50 +0100"
Shaun Lipscombe <shaun.lipscombe@gasops.co.uk> writes:
> What I don't understand though, is why have 3 different values t 'head
> and 'last. I understand that 'head works on the headers, so what use
> would t, and 'last have?
Because Lars wants uniform specifications over all gnus-treat-*
variables. I think this is a real misconception because it leads to
meaningless values for some of these variables (like this one) and because
nothing prevents you from saying 'head to many different gnus-treat-date-*, in
which case the behavior is undefined (I mean, you can't guess what will
happen).
But Lars seems to be hooked on this scheme.
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:verna@inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19
next prev parent reply other threads:[~1999-07-26 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-23 9:28 X-Sent Shaun Lipscombe
1999-07-23 10:27 ` X-Sent Kai Großjohann
1999-07-23 17:33 ` X-Sent Shaun Lipscombe
1999-07-23 18:32 ` X-Sent Aaron M. Ucko
1999-07-23 18:57 ` X-Sent Hrvoje Niksic
1999-07-24 13:10 ` X-Sent Shaun Lipscombe
1999-07-26 8:29 ` X-Sent Shaun Lipscombe
1999-07-26 13:11 ` X-Sent Karl Kleinpaste
1999-07-26 16:25 ` X-Sent Shaun Lipscombe
1999-07-26 16:46 ` Didier Verna [this message]
1999-07-26 17:25 ` X-Sent Shaun Lipscombe
1999-07-27 1:50 ` X-Sent Hrvoje Niksic
1999-08-27 21:43 ` X-Sent Lars Magne 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=qyjyag31hqh.fsf@metheny.enst.fr \
--to=verna@inf.enst.fr \
--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).