From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: X-Sent
Date: 27 Jul 1999 03:50:58 +0200 [thread overview]
Message-ID: <87n1wilv25.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Didier Verna's message of "26 Jul 1999 18:46:46 +0200"
Didier Verna <verna@inf.enst.fr> writes:
> 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.
The worst thing is that the docstrings are highly misleading. All of
them say "Valid values are nil, t, `head', `last', an integer or a
predicate."
Although those values may be technically "valid", in the case
gnus-treat-date-lapsed, only nil and `head' are really meaningful.
The docstring should be helpful about what is really going on rather
than confuse matters for the user.
The manual is apparently even worse -- it just lists the variables and
explains what the "predicate" stuff does.
next prev parent reply other threads:[~1999-07-27 1:50 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 ` X-Sent Didier Verna
1999-07-26 17:25 ` X-Sent Shaun Lipscombe
1999-07-27 1:50 ` Hrvoje Niksic [this message]
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=87n1wilv25.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).