I'd be content with the following logic:
Don't process a `system' wgetrc. If $HOME is not defined, use the
directory the Wget executable is in as $HOME (what home_dir() returns).
If $HOME/.wgetrc exists, use that; otherwise look for wget.ini in the
directory the executable is in, regardless of
Thanks tracing this one. It would never have occurred to me that the
file name c:\/foo could cause such a problem.
I see two different bugs here:
1. The routine that merges the .netrc file name with the directory
name should be made aware of Windows, so that it doesn't append
another
[...]
Cygwin considers `c:\Documents and Settings\USERNAME' to be the
home directory. I wonder if that is reachable through registry...
Does anyone have an idea what we should consider the home dir under
Windows, and how to find it?
Doesn't this depend on each user's personal
At 06:23 PM 2/8/2004, Hrvoje Niksic wrote:
Does anyone have an idea what we should consider the home dir under
Windows, and how to find it?
In Windows 2000, if I enter SET at the command prompt, I get a return
that is a listing of all of the environment variables that have been
established
Petr Kadlec wrote:
I have traced the problem down to search_netrc() in netrc.c, where the
program is trying to find the file using stat(). But as home_dir()
returns C:\ on Windows, the filename constructed looks like
C:\/.netrc, which is then probably interpreted by Windows as a name of
a
Hrvoje Niksic wrote:
Does anyone have an idea what we should consider the home dir under
Windows, and how to find it?
On Windows 2000 and XP, there are two environment variables that together
provide the user's home directory. (It may go back further than that, but I
don't have any machines
