Re: LYNX-DEV "Cannot open.." in Win95

[K. Peijnenborg]

T.E.Dickey <address@hidden> wrote
> > 
> >  
> > On Wed, 18 Mar 1998, T.E.Dickey wrote: 
> > > > On Wed, 18 Mar 1998, T.E.Dickey wrote:  
> > > > > > Setting temp=c:\tmp (and creating same) cured the "can't open" 
 
> > > >   
> > > > Part of this may have been fixed by Doug's last patch.  The other
part is  
> > > > caused by #define TEMP_SPACE "/tmp/" in userdefs.h.  What is a safe
thing  
> > > > to put there if people have no temp space defined?  
> > > for DOS: "/" 
> or "\\", if you prefer.  I meant to indicate locations that were
guaranteed
> to exist (but overlooked the NFS-mounted directories which may not be
> writable as well).
>   
> > That didn't work quite right.  I finally came up with C: but you also
need 
> > to then putenv() that as well to make lynx happy.  It will be in the
patch 
> > I am working on.   
> then "C:\\" or "C:/"  (if you don't, then you will get files written to
> arbitrary locations, making them harder to find).

The lynx dir would be better, I think.

If lynx is installed on a network, just throwing the files
somewhere local doesn't seem a nice thing to do. And this
is assuming there *is* a local drive. You can at least be
sure that the drive with lynx exists.

I think it is possible to retrieve the directory lynx (or any
executable) resides in. (It is possible in Turbo Pascal ;-))
Something like argument 0, and then parsing the dir out.
There should be a lib-function for it.

regards,

Karel