Re: lynx-dev Win32 docs patch (was: Lynx and downloading files)

[Don Adaway]

In article <address@hidden>, Doug
Kaufman <address@hidden> writes
>The problem is more complex. As in this user's case, he had a cp.exe
>program, but it was the wrong one. Making sure that there is a valid
>cp program, that follows the expected syntax, seems like a lot of
>overhead every time lynx is run.
>

As the user mentioned above may I make a comment?  The problem was self-
inflicted.  My original intention was to ensure that downloaded files
arrived in a directory of my choice.  I had discovered that files were
being downloaded to the working directory.  This was \lynx by default
and because this directory contains the all-important Lynx binaries I
preferred that they go elsewhere.  Accordingly I changed the working
directory, but this had the effect that cp.exe (in the \lynx directory)
was no longer on the path and another program called cp.exe (in the
path) was being executed.  This would not have happened had I understood
the significance of the working directory, the path, and the existence
of the SAVE_SPACE variable in the behaviour of Lynx.

The only place where the existence of the SAVE_SPACE variable is
mentioned is in the lynx.cfg file itself; none of the help files mention
it that I can find.  I feel that mention of the possible interaction
between working directory, path and SAVE_SPACE should appear somewhere;
possibly comment lines in lynx.cfg would do the trick.  It's all obvious
when you know, but then perhaps I'm the only person stupid enough to
have had this problem.

-- 
Don      chervil @ freeuk . com