Currently maintained by Micah Cowan <micah@cowan.name>.
@c man end
@c man begin SEEALSO
-GNU Info entry for @file{wget}.
+This is @strong{not} the complete manual for GNU Wget.
+For more complete information, including more detailed explanations of
+some of the options, and a number of commands available
+for use with @file{.wgetrc} files and the @samp{-e} option, see the GNU
+Info entry for @file{wget}.
@c man end
@end ignore
@end example
The space between the option accepting an argument and the argument may
-be omitted. Instead @samp{-o log} you can write @samp{-olog}.
+be omitted. Instead of @samp{-o log} you can write @samp{-olog}.
You may put several options that do not require arguments together,
like:
@cindex timeout, read
@item --read-timeout=@var{seconds}
Set the read (and write) timeout to @var{seconds} seconds. The
-``time'' of this timeout refers @dfn{idle time}: if, at any point in
+``time'' of this timeout refers to @dfn{idle time}: if, at any point in
the download, no data is received for more than the specified number
of seconds, reading fails and the download is restarted. This option
does not directly affect the duration of the entire download.
@itemx --http-password=@var{password}
Specify the username @var{user} and password @var{password} on an
@sc{http} server. According to the type of the challenge, Wget will
-encode them using either the @code{basic} (insecure) or the
-@code{digest} authentication scheme.
+encode them using either the @code{basic} (insecure),
+the @code{digest}, or the Windows @code{NTLM} authentication scheme.
Another way to specify username and password is in the @sc{url} itself
(@pxref{URL Format}). Either method reveals your password to anyone who
@item -A @var{acclist} --accept @var{acclist}
@itemx -R @var{rejlist} --reject @var{rejlist}
Specify comma-separated lists of file name suffixes or patterns to
-accept or reject (@pxref{Types of Files} for more details). Note that if
+accept or reject (@pxref{Types of Files}). Note that if
any of the wildcard characters, @samp{*}, @samp{?}, @samp{[} or
@samp{]}, appear in an element of @var{acclist} or @var{rejlist},
it will be treated as a pattern, rather than a suffix.
@item -I @var{list}
@itemx --include-directories=@var{list}
Specify a comma-separated list of directories you wish to follow when
-downloading (@pxref{Directory-Based Limits} for more details.) Elements
+downloading (@pxref{Directory-Based Limits}). Elements
of @var{list} may contain wildcards.
@item -X @var{list}
@itemx --exclude-directories=@var{list}
Specify a comma-separated list of directories you wish to exclude from
-download (@pxref{Directory-Based Limits} for more details.) Elements of
+download (@pxref{Directory-Based Limits}). Elements of
@var{list} may contain wildcards.
@item -np
This chapter contains all the stuff that could not fit anywhere else.
@menu
-* Proxies:: Support for proxy servers
+* Proxies:: Support for proxy servers.
* Distribution:: Getting the latest version.
+* Web Site:: GNU Wget's presence on the World Wide Web.
* Mailing List:: Wget mailing list for announcements and discussion.
* Reporting Bugs:: How and where to report bugs.
* Portability:: The systems Wget works on.
Wget @value{VERSION} can be found at
@url{ftp://ftp.gnu.org/pub/gnu/wget/wget-@value{VERSION}.tar.gz}
+@node Web Site
+@section Web Site
+@cindex web site
+
+The official web site for GNU Wget is at
+@url{http://www.gnu.org/software/wget/}. However, most useful
+information resides at ``The Wget Wgiki'',
+@url{http://wget.addictivecode.org/}.
+
@node Mailing List
@section Mailing List
@cindex mailing list
@cindex list
-There are several Wget-related mailing lists, all hosted by
-SunSITE.dk. The general discussion list is at
-@email{wget@@sunsite.dk}. It is the preferred place for bug reports
-and suggestions, as well as for discussion of development. You are
-invited to subscribe.
+There are several Wget-related mailing lists. The general discussion
+list is at @email{wget@@sunsite.dk}. It is the preferred place for
+support requests and suggestions, as well as for discussion of
+development. You are invited to subscribe.
To subscribe, simply send mail to @email{wget-subscribe@@sunsite.dk}
and follow the instructions. Unsubscribe by mailing to
@url{http://www.mail-archive.com/wget%40sunsite.dk/} and at
@url{http://news.gmane.org/gmane.comp.web.wget.general}.
-The second mailing list is at @email{wget-patches@@sunsite.dk}, and is
+Another mailing list is at @email{wget-patches@@sunsite.dk}, and is
used to submit patches for review by Wget developers. A ``patch'' is
a textual representation of change to source code, readable by both
humans and programs. The file @file{PATCHES} that comes with Wget
send general suggestions or bug reports to @samp{wget-patches}; use it
only for patch submissions.
-To subscribe, simply send mail to @email{wget-subscribe@@sunsite.dk}
-and follow the instructions. Unsubscribe by mailing to
-@email{wget-unsubscribe@@sunsite.dk}. The mailing list is archived at
+Subscription is the same as above for @email{wget@@sunsite.dk}, except
+that you send to @email{wget-patches-subscribe@@sunsite.dk}, instead.
+The mailing list is archived at
@url{http://news.gmane.org/gmane.comp.web.wget.patches}.
+Finally, there is the @email{wget-notify@@addictivecode.org} mailing
+list. This is a non-discussion list that receives commit notifications
+from the source repository, and also bug report-change notifications.
+This is the highest-traffic list for Wget, and is recommended only for
+people who are seriously interested in ongoing Wget development.
+Subscription is through the @code{mailman} interface at
+@url{http://addictivecode.org/mailman/listinfo/wget-notify}.
+
@node Reporting Bugs
@section Reporting Bugs
@cindex bugs
@cindex bug reports
@c man begin BUGS
-You are welcome to send bug reports about GNU Wget to
-@email{bug-wget@@gnu.org}.
+You are welcome to submit bug reports via the GNU Wget bug tracker (see
+@url{http://wget.addictivecode.org/BugTracker}).
Before actually submitting a bug report, please try to follow a few
simple guidelines.
Please try to ascertain that the behavior you see really is a bug. If
Wget crashes, it's a bug. If Wget does not behave as documented,
it's a bug. If things work strange, but you are not sure about the way
-they are supposed to work, it might well be a bug.
+they are supposed to work, it might well be a bug, but you might want to
+double-check the documentation and the mailing lists (@pxref{Mailing
+List}).
@item
Try to repeat the bug in as simple circumstances as possible. E.g. if
``special'' features of any particular Unix, it should compile (and
work) on all common Unix flavors.
-Various Wget versions have been compiled and tested under many kinds
-of Unix systems, including GNU/Linux, Solaris, SunOS 4.x, OSF (aka
-Digital Unix or Tru64), Ultrix, *BSD, IRIX, AIX, and others. Some of
-those systems are no longer in widespread use and may not be able to
+Various Wget versions have been compiled and tested under many kinds of
+Unix systems, including GNU/Linux, Solaris, SunOS 4.x, Mac OS X, OSF
+(aka Digital Unix or Tru64), Ultrix, *BSD, IRIX, AIX, and others. Some
+of those systems are no longer in widespread use and may not be able to
support recent versions of Wget. If Wget fails to compile on your
system, we would like to know about it.
@email{wget@@sunsite.dk} where the volunteers who maintain the
Windows-related features might look at them.
+Support for building on MS-DOS via DJGPP has been contributed by Gisle
+Vanem; a port to VMS is maintained by Steven Schweda, and is available
+at @url{http://antinode.org/}.
+
@node Signals
@section Signals
@cindex signal handling
projects / wget / blobdiff