home *** CD-ROM | disk | FTP | other *** search
- Organization: Carnegie Mellon, Pittsburgh, PA
- Path: sparky!uunet!spool.mu.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!bb3.andrew.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
- Newsgroups: comp.sys.amiga.misc
- Message-ID: <sfIUNS200hsBAouGkY@cs.cmu.edu>
- Date: Mon, 11 Jan 1993 18:44:30 -0500
- From: Michael Witbrock <mjw+@cs.cmu.edu>
- Subject: Re: Commodity question
- In-Reply-To: <38444@cbmvax.commodore.com>
- References: <38291@cbmvax.commodore.com> <wanderer.03pd@tcsi.appleton.mil.wi.us> <crystal.726437518@glia> <1993Jan7.222820.13563@hubcap.clemson.edu> <38416@cbmvax.commodore.com> <crystal.726524912@glia>
- <38444@cbmvax.commodore.com>
- Distribution: world
- Lines: 17
-
- Excerpts from netnews.comp.sys.amiga.misc: 9-Jan-93 Re: Commodity
- question Ross H. - Manuals@cbmvax (2885)
-
-
- > Still, I am only quibbling. Your basic point is valid. I'll look into how
- > we could improve our docs to take account of possible newbie reaction to
- > unexplained disk contents.
-
-
- You could just consistently put a "contents" file on the disk, and a
- pointer to it in the manual.
- It could even have a line or two about each program. It's not worth
- putting every little monitor, library, datatype, keymap etc in the
- printed docs - the utility gained wouldn't be worth the oxygen
- production lost from the trees.
-
- Of course, people could then worry about virii messing with the contents file.
-