> > > There are still a number of settings which are generally configured > > in userdefs.h, even after configure is used, and which can not be set > ^^^^^ > I always edit userdefs.h _before_ running the configure script. Is it > irrelevant whether one edits userdefs.h before or after? yes (order does not matter, since userdefs.h isn't used during the configure process - though in principal it could be: for tin's configure script I found it worked best to make compile-checks including tin's header files, but _that_ was to make the missing-prototype checks work). > __Henry -- Thomas E. Dickey [EMAIL PROTECTED] http://www.clark.net/pub/dickey
- Re: lynx-dev (patch) userdefs.h & lynxcfg: T.E.Dickey
- Re: lynx-dev (patch) userdefs.h & lynxcfg: T.E.Dickey
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Larry W. Virden
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Henry Nelson
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Klaus Weide
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Doug Kaufman
- Re: lynx-dev (patch) userdefs.h & lynxcfg: T.E.Dickey
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Henry Nelson
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Henry Nelson
- Re: lynx-dev (patch) userdefs.h & lynxcfg: Doug Kaufman
- lynx-dev userdefs.h vs config (was different) T.E.Dickey
- lynx-dev userdefs.h vs config (was different) Philip Webb
- Re: lynx-dev userdefs.h vs config (was different) Doug Kaufman