Re: LYNX-DEV lynx reading *.gz file

[Larry W. Virden, x2487]

> If you compiled Lynx yourself, you didn't read the documentation
> that is necessary to read before installing.

Or in reading all that doc, trying to comprehend all the stuff that someone
who has never even compiled a package before, you missed the fact that
at the _bottom_ of the userdefs.h file there are a set of full pathnames
for programs.

I've compiled packages for years, and missed this one myself for several
weeks.

Don't take it so hard.  It takes a while.  I recommend also going back
and doing an occasional reread every other time or so that you configure
and build a new lynx.  Between updates and growing more comfortable
doing the actual steps of configuration, and becoming more familar with
Lynx, you may find other things that you really want to change in the
way that lynx compiled.

P.S.  If anyone is working on instructions for the novice (you know
- Building Lynx for Dummies, or whatever), be sure to recommend that
once they get a working lynx that they NOT copy a new one overtop of
it until the new one is proven to work.  I had gotten lazy about 
lynx and patches 'always' working, and just spend two days without
a working lynx, trying to recover from a recently applied patch which
left me without a working lynx.  Not a pretty picture.  I kept trying
to figure out where the problem was, and compiling various variations
until I found one that worked.  Shrug.
-- 
Larry W. Virden                 INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;