Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!samsung!uakari.primate.wisc.edu!nic.MR.NET!thor.acc.stolaf.edu!hopp
From: hopp@thor.acc.stolaf.edu (Eric D. Hopp)
Newsgroups: comp.sys.amiga
Subject: Re: Requests from CATS for info on improve
Keywords: manuals man on-line
Message-ID: <11817@thor.acc.stolaf.edu>
Date: 28 Mar 90 02:05:54 GMT
References: <90031520084142@masnet.uucp> <869@jc3b21.UUCP>
Reply-To: hopp@thor.acc.stolaf.edu (Eric Hopp)
Organization: St. Olaf College; Northfield, MN
Lines: 25

In article <869@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes:

...quote of a thread I didn't read...

>     A man command wouldn't be the best solution.  Printed manuals would be
>better.  However, the man command itself could reside in the C:
>directory--it wouldn't have to be big.  The information it displayed could
>reside on a separate disk.  The user would type "man" or press the "Help"
>key or click on a "Help" icon--whatever interface makes the most sense--and
>see a requester advising him to insert disk "ManualText" (or whatever) in a
>drive.  Even the novice user could make that work, I think.  It would be a
>lot cheaper than providing printed manuals.  That means it is a lot more
>likely to get done.

   Interesting.  I've got a script version of "man" in my S:
directory.  It takes one argument; the name of the text file to read.
It hunts for it in man:, and reports its absence if it didn't exist.
If it does exist, it calls more on it.
   I'm using a hard disk, and I either got man files from the ARP
distrobution or made them myself.
   It sure would be neat if Commodore sold/bundled the man files for
the C: commands and the .library calls.

							-eric hopp
							 hopp@stolaf.edu