🚀 go-pugleaf

In article <Bv7LE3.DvK@news.cso.uiuc.edu> jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
...

>sit there and not actually index anything.  Also, for some reason I can't get  
>my local man pages to index like the NeXT-supplied ones do; with the  
>descriptions and coming up as "blah" or "blah(1)" instead of "man1/blah.1".  I  
>can see that the nice descriptions come from the 'whatis' file, but is there a  
>relatively painless way to make that 'whatis' file?  I'm not in any mood to  
>summarize each man page I've got manually.
>
>Back to the thread of 3.0's DL; in an attempt to duplicate NeXT's method for  
>output display of manpages in DL, I simply linked the additional files for  
>formatting the manpage output and the directory icon (.roffArgs,  
>displayCommand and .dir.tiff respectively).  I linked from  
>/NextLibrary/Documentation/ManPages to /usr/local/man.
....
>-- Jeff (jeffo@uiuc.edu)
>-- NeXTmail ok

I had trouble with this under 2.2 and, now, 3.0.  For 2.2, I had to install
the man pages with "installman".  Nothing else worked - even if I duplacted
the commands installman was executing.  Then, under 3.0, I tried to just
index them w/o any of the indexing files.  That didn't work.  I then tried
installman.  It's gone.  I then tried to copy the indexing resource files 
that were in the NextLibrary man pages.  Still wasn't right.  Finally, I
copied the index file from the NextLibrary man pages and did an update.
That worked.  Jeez, I hope this isn't the "right" way to do this.  I'll
have to read the docs for DL sometime - if I can find it.

I do appreciate having BackSpace.  That, Terminal and Edit were very nice
surprises, indeed.
-- 
  Craig Pratt                                          pcnot4me@cs.montana.edu
  Montana State University, Bozeman MT            gcp1070@msu.oscs.montana.edu
    Yes, you too can now test and debug Microsoft Windows NT for the special
         introductory price of $69!!  That's right, *you* pay *them*!