Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!wyse!adyer
From: adyer@wyse.wyse.com (Andrew Dyer x2446)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Microsoft C 6.0 - Documentation format
Message-ID: <2706@wyse.wyse.com>
Date: 2 May 90 18:41:53 GMT
References: <8580@cg-atla.agfa.com# <4602@hub.UUCP> <223@metapyr.UUCP> <686@ssbell.IMD.Sterling.COM> <3304@ssc-vax.UUCP> <4775@daffy.cs.wisc.edu> <1990Apr27.115023.3401@watserv1.waterloo.edu> <3532.263eb7bf@wums.wustl.edu>
Sender: news@wyse.wyse.com
Reply-To: adyer@milo.UUCP (Andrew Dyer x2446)
Organization: Wyse Technology
Lines: 14

My solution was to use the 'HELPMAKE' program to unencode the .hlp
files included with the system. After that, I ran the whole mess through
MicroEmacs and separated the wheat from the chaff. I divided up the 
sections into separate named files, put them in a special directory, and
I can then load them into emacs in a separate buffer when I need them.

There are some drawbacks, of course. There is no automatic hyperlink-like
capability, but at least I'm freed from using the quickC editor! :-)
Now, if I just had the cashola to spring for a package with codeview for
debugging....
{uunet, mips, decwrl}!wyse!adyer  adyer@wyse.com
 Now I'm having INSIPID THOUGHTS about the beatiful, round
 wives of HOLLYWOOD MOVIE MOGULS encased in PLEXIGLASS CARS
 and being approached by SMALL BOYS selling FRUIT..