Using wget in a cygwin bash shell from Win2K Pro. All other browsing works fine
with other clients. Where can I start looking? Thanks.
$ wget -d http://www.google.com
DEBUG output created by Wget 1.9.1 on cygwin.
--18:04:18-- http://www.google.com/
=> `index.html'
Resolving www.googl
David Fritz <[EMAIL PROTECTED]> writes:
> Hrvoje Niksic wrote:
>> Thanks for the patch, I've now applied it to CVS.
>> You might want to add a comment in front of fake_fork() explaining
>> what it does, and why. The comment doesn't have to be long, only
>> several sentences so that someone readin
Hrvoje Niksic wrote:
Thanks for the patch, I've now applied it to CVS.
You might want to add a comment in front of fake_fork() explaining
what it does, and why. The comment doesn't have to be long, only
several sentences so that someone reading the code later understands
what the heck a "fake for
David Fritz <[EMAIL PROTECTED]> writes:
> Ok, I'll submit a patch latter tonight. Do you think it would be a
> good idea to include README.fork in windows/ (the directory with the
> Windows Makefiles, etc. in it)?
I don't think that's necessary. Simply explain how the fork emulation
works in ms
Hrvoje Niksic wrote:
Thanks for the patch, I've now applied it to CVS.
You might want to add a comment in front of fake_fork() explaining
what it does, and why. The comment doesn't have to be long, only
several sentences so that someone reading the code later understands
what the heck a "fake for
Juhana Sadeharju <[EMAIL PROTECTED]> writes:
> Command: "wgetdir http://liarliar.sourceforge.net";.
> Problem: Files are named as
> content.php?content.2
> content.php?content.3
> content.php?content.4
> which are interpreted, e.g., by Nautilus as manual pages and are
> displayed as plain te
Thanks for the patch, I've now applied it to CVS.
You might want to add a comment in front of fake_fork() explaining
what it does, and why. The comment doesn't have to be long, only
several sentences so that someone reading the code later understands
what the heck a "fake fork" is and why we're p
Hrvoje Niksic wrote:
For now I'd start with applying David's patch, so that people can test
its functionality. It is easy to fix the behavior of `wget -q -b'
later.
David, can I apply your patch now?
Sure.
The attached patch corrects a few minor formatting details but is otherwise
identical to t
Hello. This is report on some wget bugs. My wgetdir command looks
the following (wget 1.9.1):
wget -k --proxy=off -e robots=off --passive-ftp -q -r -l 0 -np -U Mozilla $@
Bugs:
Command: "wgetdir http://www.directfb.org";.
Problem: In file "www.directfb.org/index.html" the hrefs of type
"/screen
"=?utf-8?B?0JLQsNGB0LjQu9C10LLRgdC60LjQuSDQodC10YDQs9C10Lk=?=" <[EMAIL PROTECTED]>
writes:
> url: list.php?cat_id=Àêñåññóàðû è êàáåëè
>
> Wget 1.8.2 on freebsd4.7. escape url befor save to disk.
> Wget 1.9.1 on freebsd4.7. not escape url befor save to disk.
>
> How can I use 1.9.1 with escaping?
For now I'd start with applying David's patch, so that people can test
its functionality. It is easy to fix the behavior of `wget -q -b'
later.
David, can I apply your patch now?
I use some scripts that read this files and when you change format this scripts break.
I think new option must add to old, but not replace. And user may check what are he
want!
> > url: list.php?cat_id=ÃâÃÂÃÂÃÂÃÂÃÂÃÂà ÃÂààÃÂÃ
> > ÃÂÃÂÃÂÃÂ
> >
> > Wget 1.8.2 on freebsd4.7. escape url befor s
url: list.php?cat_id=ÃÃ Ã ÃÃ
Wget 1.8.2 on freebsd4.7. escape url befor save to disk.
Wget 1.9.1 on freebsd4.7. not escape url befor save to disk.
How can I use 1.9.1 with escaping?
--restrict-file-names - not work!
> From: David Fritz [mailto:[EMAIL PROTECTED]
> Subject: Re: [PATCH] A working implementation of fork_to_background()
> The current patch attempts to emulate the behavior of the
> Unix version. AFAICT,
> this and the following suggestion apply equally well to the
> existing (Unix) code.
I ag
14 matches
Mail list logo
