Re: Small bug in Wget manual page
On Wednesday 15 June 2005 04:57 pm, Ulf Harnhammar wrote: On Wed, Jun 15, 2005 at 03:53:40PM -0500, Mauro Tortonesi wrote: the web pages (including the documentation) on gnu.org have just been updated. Nice! I have found some broken links and strange grammar, though: * index.html: There are archives of the main GNU Wget list at ** fly.cc.fer.hr ** www.geocrawler.com (neither works) * wgetdev.html ** Translation Project page (doesn't work) * faq.html ** 3.1 [..] Yes, starting from version 1.10, GNU Wget support files larger than 2GB. (should be supports) fixed. thank you very much. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it Institute for Human Machine Cognition http://www.ihmc.us GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
Re: Small bug in Wget manual page
On Wednesday 15 June 2005 05:14 pm, Ulf Harnhammar wrote: On Wed, Jun 15, 2005 at 11:57:42PM +0200, Ulf Harnhammar wrote: * faq.html ** 3.1 [..] Yes, starting from version 1.10, GNU Wget support files larger than 2GB. (should be supports) ** 2.0 How I compile GNU Wget? (should be How do I) fixed. thank you very much. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it Institute for Human Machine Cognition http://www.ihmc.us GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
Re: Small bug in Wget manual page
Mauro Tortonesi [EMAIL PROTECTED] writes: this seems to be already fixed in the 1.10 documentation. Now that 1.10 is released, we should probably update the on-site documentation.
Re: Small bug in Wget manual page
On Wednesday 15 June 2005 02:05 pm, Hrvoje Niksic wrote: Mauro Tortonesi [EMAIL PROTECTED] writes: this seems to be already fixed in the 1.10 documentation. Now that 1.10 is released, we should probably update the on-site documentation. i am doing it right now. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it Institute for Human Machine Cognition http://www.ihmc.us GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
Re: Small bug in Wget manual page
On Wednesday 15 June 2005 02:16 pm, Mauro Tortonesi wrote: On Wednesday 15 June 2005 02:05 pm, Hrvoje Niksic wrote: Mauro Tortonesi [EMAIL PROTECTED] writes: this seems to be already fixed in the 1.10 documentation. Now that 1.10 is released, we should probably update the on-site documentation. i am doing it right now. the web pages (including the documentation) on gnu.org have just been updated. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it Institute for Human Machine Cognition http://www.ihmc.us GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
Re: Small bug in Wget manual page
On Wed, Jun 15, 2005 at 03:53:40PM -0500, Mauro Tortonesi wrote: the web pages (including the documentation) on gnu.org have just been updated. Nice! I have found some broken links and strange grammar, though: * index.html: There are archives of the main GNU Wget list at ** fly.cc.fer.hr ** www.geocrawler.com (neither works) * wgetdev.html ** Translation Project page (doesn't work) * faq.html ** 3.1 [..] Yes, starting from version 1.10, GNU Wget support files larger than 2GB. (should be supports) // Ulf
Re: Small bug in Wget manual page
On Wed, Jun 15, 2005 at 11:57:42PM +0200, Ulf Harnhammar wrote: * faq.html ** 3.1 [..] Yes, starting from version 1.10, GNU Wget support files larger than 2GB. (should be supports) ** 2.0 How I compile GNU Wget? (should be How do I) // Ulf
Re: Small bug in Wget manual page
On Thursday 02 June 2005 09:33 am, Herb Schilling wrote: Hi, On http://www.gnu.org/software/wget/manual/wget.html, the section on protocol-directories has a paragraph that is a duplicate of the section on no-host-directories. Other than that, the manual is terrific! Wget is wonderful also. I don't know what I would do without it. --protocol-directories Use the protocol name as a directory component of local file names. For example, with this option, wget -r http://host will save to http/host/... rather than just to host/ Disable generation of host-prefixed directories. By default, invoking Wget with -r http://fly.srk.fer.hr/ will create a structure of directories beginning with fly.srk.fer.hr/. This option disables such behavior. this seems to be already fixed in the 1.10 documentation. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it Institute for Human Machine Cognition http://www.ihmc.us GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
A small bug in wget
The bug appers if you use another output file and try to convert the url's at the same time. If you try to execute the following: wget -k -O myFile http://www.stud.ntnu.no/index.html The file will not convert, becuse wget do not locate the file index.html since the output-file is not index.html but myFile.
Re: small bug in wget manpage: --progress
Noel Koethe [EMAIL PROTECTED] writes:
the wget 1.8.1 manpage tells me:
--progress=type
Select the type of the progress indicator you wish to
use. Legal indicators are ``dot'' and ``bar''.
The ``dot'' indicator is used by default. It traces
the retrieval by printing dots on the screen, each dot
representing a fixed amount of downloaded data.
But it looks like the default is bar.
Yes. Thanks for the report; I'm about to apply this fix.
2002-04-15 Hrvoje Niksic [EMAIL PROTECTED]
* wget.texi (Download Options): Fix the documentation of
`--progress'.
Index: doc/wget.texi
===
RCS file: /pack/anoncvs/wget/doc/wget.texi,v
retrieving revision 1.64
diff -u -r1.64 wget.texi
--- doc/wget.texi 2002/04/13 22:44:16 1.64
+++ doc/wget.texi 2002/04/15 20:52:28
@@ -625,10 +625,15 @@
Select the type of the progress indicator you wish to use. Legal
indicators are ``dot'' and ``bar''.
-The ``dot'' indicator is used by default. It traces the retrieval by
-printing dots on the screen, each dot representing a fixed amount of
-downloaded data.
+The ``bar'' indicator is used by default. It draws an ASCII progress
+bar graphics (a.k.a ``thermometer'' display) indicating the status of
+retrieval. If the output is not a TTY, the ``dot'' bar will be used by
+default.
+Use @samp{--progress=dot} to switch to the ``dot'' display. It traces
+the retrieval by printing dots on the screen, each dot representing a
+fixed amount of downloaded data.
+
When using the dotted retrieval, you may also set the @dfn{style} by
specifying the type as @samp{dot:@var{style}}. Different styles assign
different meaning to one dot. With the @code{default} style each dot
@@ -639,11 +644,11 @@
files---each dot represents 64K retrieved, there are eight dots in a
cluster, and 48 dots on each line (so each line contains 3M).
-Specifying @samp{--progress=bar} will draw a nice ASCII progress bar
-graphics (a.k.a ``thermometer'' display) to indicate retrieval. If the
-output is not a TTY, this option will be ignored, and Wget will revert
-to the dot indicator. If you want to force the bar indicator, use
-@samp{--progress=bar:force}.
+Note that you can set the default style using the @code{progress}
+command in @file{.wgetrc}. That setting may be overridden from the
+command line. The exception is that, when the output is not a TTY, the
+``dot'' progress will be favored over ``bar''. To force the bar output,
+use @samp{--progress=bar:force}.
@item -N
@itemx --timestamping
