From: Steven L Baur <steve@miranova.com>
Subject: Re: Q: Cross posted articles
Date: 23 Feb 1996 14:45:02 -0800 [thread overview]
Message-ID: <m23f818xw1.fsf@deanna.miranova.com> (raw)
In-Reply-To: Mark Borges's message of 23 Feb 1996 12:30:08 -0800
>>>>> "mb" == Mark Borges <mdb@cdc.noaa.gov> writes:
>>> Christopher Davis(ckd) wrote:
ckd> Try this trick:
ckd> Telnet to the news server's nntp port.
ckd> Type "list overview.fmt".
ckd> See if it includes a line "Xref:full".
ckd> It probably doesn't.
mb> good guess!
mb> mine doesn't (see below). Is this one of those things I "should
mb> complain bitterly to the NetNews administrators" about?
Yes. You can be thankful you're running a real INN server though.
The one from Netscape has some horrible bugs in it that they refuse to
fix.
ckd> (PS to Lars: maybe a Red Gnus feature? M-x gnus-check-for-evil-nov ? :)
mb> Does this mean my NOV is eVIl? (I don't really understand the full
mb> repercussions, apart from the obvious that scoring on Xref won't
mb> work). Would I be better served by setting g-n-i-e:
gnus-nov-is-evil is overkill. You could say gnus-nov-is-evil is evil,
since setting it disables use of overview with nnml as well. Setting
nntp-nov-is-evil is sufficient.
Speaking for myself, I have to have crossposts killed once read.
Reading news is too annoying without it. The main thing you lose is
stuff like gnus-fetch-old-headers which doesn't work without NOV.
I started on a workaround patch to use XHDR[*] to get Xref:, but it got
totally broken when Lars overhauled nntp.el, and I haven't gotten back
to it.
[*]You get overview info from an INN server by issuing the command
XOVER from-to
If this is missing Xref: data, it may be obtained by issuing the command
XHDR XREF from-to
and then grafting the results onto the data obtained from XOVER to get
the same effect.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-02-23 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v0wwx5zkwpt.fsf@corinth.cs.uni-magdeburg.de>
[not found] ` <w8sivhh6570.fsf@aegir.ifi.uio.no>
[not found] ` <x43f869lcc.fsf@fly.cnuce.cnr.it>
[not found] ` <w47mxddh2e.fsf@loiosh.kei.com>
1996-02-23 20:30 ` Mark Borges
1996-02-23 22:45 ` Steven L Baur [this message]
1996-02-24 7:44 ` 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=m23f818xw1.fsf@deanna.miranova.com \
--to=steve@miranova.com \
/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).