From: Russ Allbery <rra@stanford.edu>
Subject: Re: [0.95]: faulty display of article in pgnus Summary buffer
Date: 25 Sep 1999 05:04:19 -0700 [thread overview]
Message-ID: <ylzoybi4e4.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "24 Sep 1999 18:58:33 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> There was no Lines header, which explains why Gnus reported zero lines.
You really want to pull your lines value from overview rather than from
the Lines header if available. The Lines header is discouraged, and may
even be deprecated, in USEFOR, due to the fact that it's unreliable in
practice (leading to errors just like the above). Overview is
"guaranteed" correct by the local server.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~1999-09-25 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ruooggvp8hn.fsf@g.wolfram.com>
1999-07-30 11:43 ` Slawek Zak
1999-07-30 17:35 ` Bill White
1999-09-24 16:58 ` Lars Magne Ingebrigtsen
1999-09-25 12:04 ` Russ Allbery [this message]
1999-09-25 12:10 ` Lars Magne Ingebrigtsen
1999-09-25 13:31 ` Russ Allbery
1999-09-25 13:46 ` 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=ylzoybi4e4.fsf@windlord.stanford.edu \
--to=rra@stanford.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).