[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Windows 7 makes wget less intuitive

From: Paul Wratt
Subject: Re: [Bug-wget] Windows 7 makes wget less intuitive
Date: Thu, 1 Dec 2011 07:55:29 +1300

the initial post is unclear on how wget is initiated, but it implied
"non-commandline use" in my view.

I agree with other post, if run from cmd or "run box" it should
perform as expected, (I have used the script from --no-clobber
--convert-links thread successfully on win7 64bit), but I think there
is a small issue present, one I can not test atm


On Thu, Dec 1, 2011 at 7:43 AM, Henrik Holst
<address@hidden> wrote:
> Ah, having tread the whole thread... I now see that this is when running
> wget from a desktop shortcut?
> Den 30 nov 2011 19:40 skrev "Henrik Holst" <address@hidden>:
>> I might not understand the problem then (not a win user), but on my system
>> I very much want wget to download the files to the current directory (of my
>> user). And that is also how it works under Linux.
>> Or does current directory mean "where the exe is" under win? If so then I
>> of course meant the directory the user stands in the console, but we are
>> perhaps not talking about a console usage even?
>> Den 30 nov 2011 19:35 skrev "Micah Cowan" <address@hidden>:
>>> A cwd to where? Normally one wants to download into the current
>>> directory (particularly if you have placed wget's location in the PATH).
>>> If you want it somewhere else, just use the -P option.
>>> -mjc
>>> (2011年11月30日 10:31), Henrik Holst wrote:
>>> > Could this be solved by having wget do a change to cwd, when running on
>>> > windows. Or something like that?
>>> >
>>> > /henrik holst
>>> > Den 30 nov 2011 18:31 skrev "David H. Lipman" <address@hidden>:
>>> >
>>> >> From: "Paul Wratt" <address@hidden>
>>> >>
>>> >>> this may have something to do with "working directory" which when an
>>> >>> exe is run from a shortcut, uses the exe folder as the default path.
>>> >>> Some testing on win7 is needed to clarify this issue, as that "Program
>>> >>> Files" path is used for 32bit apps on 64bit installation..
>>> >>>
>>> >> If the command is NOT in the PATH then you have to be in the directory
>>> >> where the command
>>> >> exists and when you run the command it will drop the downloaded files
>>> >> there.  When the
>>> >> command and dependencies are in the PATH then all I have to do is open
>>> a
>>> >> Command Prompt,
>>> >> type "Y:" and run a FQ WGET command and the file(s) ovtained will be in
>>> >> the "Y:" drive.  I
>>> >> dion't think the behaviour is any different for Win64 vs. Win32.
>>> >>
>>> >> --
>>> >> Dave
>>> >> Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
>>> >> http://www.pctipp.ch/downloads/dl/35905.asp
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]