karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) (03/18/88)
COK@PSUVMA.BITNET writes:
Path: tut.cis.ohio-state.edu!ukma!psuvm.bitnet!cok
From: COK@PSUVMA.BITNET (R. W. F. Clark)
Newsgroups: news.admin,talk.bizarre
Keywords: Mescaline-flavored Jell-O
Date: 14 Mar 88 19:35:54 GMT
References: <4955@uwmcsd1.UUCP> <322@jc3b21.UUCP> <3171@chinet.UUCP> <8393@eddie.MIT.EDU> <1426@homxb.UUCP>
Followup-To: news.admin,news.groups
Organization: Syd Barrett Cabal & The Harlequinade
Lines: 665
Xref: tut.cis.ohio-state.edu news.admin:981 talk.bizarre:3004
Why did this article claim to be 665 lines long, but in fact was about
60?
[And Cindy: You still don't know how to use a text-editor. You
_don't_ have to quote the original article, the article it was
following up, the article _that_ article was following up, _et sic
cetera_. Do try to achieve higher quality with your postings.]
You're developing a serious sunburn on your upper lip, ifyanowhatimean.CLT@PSUVMA.BITNET (Merlin of Chaos) (03/18/88)
The article cited claims to be 665 lines long for the same reason that this one claims to be 665 lines long. Simply, the software here at Penn State does not include a line count when the article is sent. Therefore, to prevent other people's software from choking when no line count is found, we posters include a ficticious line count. A line count that is blatently wrong may be misleading, but in the case of a posting to talk.bizarre, it may also be related to the topic of the article. The use of a line length of 666 for some time sprang from a series of articles regarding the occult, and the subsequent flaming. ------- c1t@ecl.psu.edu (preferred) | clt%psuvma.BITNET@psuvax1.uucp | I can't help it if our clt%psuvma.BITNET@psuvax1.cs.psu.edu | software's broke, can I? "rutgers|ukma"!psuvax1!psuvma.BITNET!clt |