Re: lynx-dev problem with LYNX_TEMP_SPACE?

[dickey]

> 
> > > The temp files created are the files which have been uncompressed by  
>                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> > > e.g. gzip (gunzip) and are then passed to a second program for reading.  
> > > In mime.types:  
> > >    application/octet-stream          gz  
> > >    text/x-archive                    arc  
> > > In mailcap:  
> > >    application/octet-stream; /usr/local/bin/gzip -d %s  
> > >    text/x-archive; /usr/local/bin/most %s  
>  
> > well, I did that (on Linux) and it works properly.  I guess I need more 
> > information.  Here's my trace: 
> [...] 
> > ProcessMailcapFile: Loading file '/usr/local/lib/mosaic/mailcap'. 
> > ProcessMailcapFile: Could not open '/usr/local/lib/mosaic/mailcap'. 
> > ProcessMailcapFile: Loading file '/home/tom/.mailcap'. 
> > ProcessMailcapFile: Could not open '/home/tom/.mailcap'. 
> [...] 
> > HTLoadExtensionsConfigFile: Loading file 
> > '/usr/local/lib/mosaic/mime.types'. 
> > HTLoadExtensionsConfigFile: Could not open 
> > '/usr/local/lib/mosaic/mime.types'. 
> > HTLoadExtensionsConfigFile: Loading file '/home/tom/.mime.types'. 
> > HTLoadExtensionsConfigFile: Could not open '/home/tom/.mime.types'. 
>  
> Lynx never got your extension definitions nor information on how to 
> handle them, so it does not "farm out" decompression.  Using libz? 

I'll check - I was relying on file access times to find the mailcap
and mime.types which were read (mailcap was under /etc, and mime.types
under /var/lib/httpd/conf).  It helps to have a second pair of eyes.
  
> I don't mind if you completely fix this bug.  Might be an area to look 
> at in the next development round. 

aside from an annoyance I've encountered in download permissions, and
some wrapup on configuration (plus a couple of LP's fixes that I put off
til this morning), there's really only documentation to review.
  
> __Henry 


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