Re: lynx-dev comments on "compile time settings"

[dickey]

> 
> Some things that ought to change, but not until after 2.8.1 is 
> released... 
>  
> Currently, as soon as you go to the INFO page ('='), temp files are 
> immediately created to hold the "compile time settings" and "your 
> lynx.cfg" pages.  I think these should be created on demand.  I also 
I thought of that, but didn't know how (suggestions are welcome - I see you
are doing that here).

afaik, if I pass the info-page to Lynx, the related pages have to be
available.

> find it ugly that (in "advanced" user mode, or on the INFO page) these 
> show temp file URLs. 
>  
> I'd like to suggest that Lynx adopt the Netscapism of "about:" URLs. 
> These would be internal URLs, contents constructed on demand.  Currently 
> we have LYNXKEYMAP: as the back-end of the "K" KEYMAP command; and the 
> above two pages.  I propose these be changed to "about:compile", 
> "about:lynx.cfg", and "about:keymap".  We may later want to add other 
> "about:" choices; and I may have forgotten others.  It might also make 
> sense to change ^H HISTORY and "V" VLINKS to "about:history" and 
> "about:visited".  I dunno. 
ok - I'll look into this.  (Right now I've switched to xterm because I've
both waiting for your input on NSL_FORK, and because I need a break from
Lynx and vile).
  
> Basically, it bugs me any time Lynx shows me a temp file name which is 
> some detail of Lynx's internal implementation.  I'd rather have it hide 
> these all behind opaque internal URL names. 
>  
> If the "about:" name seems too derivative, we could use "lynx:" instead, 
> i.e. "lynx:compile", "lynx:cfg", "lynx:keymap", etc. 

sounds fine.  I just hadn't thought about it that way.
  
> >Bela< 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey