Thread View: comp.sys.next.misc
2 messages
2 total messages
Started by Rob Francis
Wed, 15 Apr 1992 01:13
the thread on RTF and SEF
Author: Rob Francis
Date: Wed, 15 Apr 1992 01:13
Date: Wed, 15 Apr 1992 01:13
18 lines
1375 bytes
1375 bytes
I am one of those people Jess mentioned. I read csnm for information, and don't post too often unless I've got some information to share. I end up missing a lot of the information that comes along because I put anything that starts with Re: in my KILL file. If I had more time, I'd sort through and see the answers to questions I often have. I just don't have time to wade through the Re: RTF/SEF topics. It's a bummer, and I've love to see those discussions move elsewhere. Usenet has helped me find answer answer to problems many times, (I got about 20 replies on compiling elm -thanks to everyone that answered me) it's a great resource to have. The point is, I should speak up and say, "I agree with Jess. Please let this die." If you want to reply to me, I'll answer email, but seeing as how anything that starts with Re: gets junked, a flame on the net won't even help. (-: -rob francisr@indiana.edu
Re: the thread on RTF and SEF
Author: Edward Vielmetti
Date: Wed, 15 Apr 1992 02:26
Date: Wed, 15 Apr 1992 02:26
21 lines
1515 bytes
1515 bytes
I've found that a good way to plow through comp.sys.next.* and
the other comp.sys.* groups that occasionally have good stuff but
way too much to read all at once is to use the "comp.sys" WAIS
server that's running at the U of North Carolina. There's a
WAIS client for the NeXT that's said to be quite good. Point
the client at the server and start looking for your favorite
authors or topics. It's not the same as reading straight through
the group, but who has time for that now days? See think.com:/wais/
for details.
As an aside, WAIS is a good argument for posting things in MIME
format rather than in NewsChewer style. Mark the RTF parts with
Content-type: text/rtf; they're just about readable by poor dumb
humans, shouldn't be too hard to cook up an rtf-to-ascii for people
with non-NeXT screens on their laps, and they're way more searchable
and indexable than a big blob of uuencode.
--
Edward Vielmetti, vice president for research, MSEN Inc. emv@msen.com
MSEN Inc., 628 Brooks, Ann Arbor MI 48103 +1 313 741 1120
MIME mail cheerfully accepted. "We tried that, and it didn't matter."
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads