From: Greg Stark <gsstark@MIT.EDU>
Subject: Re: looking for references headers for the ^ command
Date: 22 May 1997 18:22:26 -0400 [thread overview]
Message-ID: <ycqraezb10d.fsf@g61-148.citenet.net> (raw)
In-Reply-To: Justin Sheehy's message of 21 May 1997 21:01:03 -0400
Justin Sheehy <dworkin@ccs.neu.edu> writes:
> This would defeat the entire purpose of NOV, which is to make it
> unnecessary to read the entire articles.
>
> If the NOV data is not going to be sufficient, then don't bother
> providing it at all.
You misunderstand, i've looked at it now, the current logic is to use the NOV
data except when it's the current article in which case Gnus looks for the
actual fields. Going back to the original source makes sense for most
situations in which the NOV data is actually generated based on real
references headers.
What i'm asking for is for Gnus to fall back on the NOV data if it exists and
the real headers don't work. i've looked at the source and it should be small
change and it won't affect normal cases where the actual headers are valid.
greg
next prev parent reply other threads:[~1997-05-22 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-21 21:30 Greg Stark
1997-05-22 1:01 ` Justin Sheehy
1997-05-22 22:22 ` Greg Stark [this message]
1997-05-24 3:48 ` 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=ycqraezb10d.fsf@g61-148.citenet.net \
--to=gsstark@mit.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).