Mauro Tortonesi wrote:
> are there __REALLY__ systems which do not support inet_aton? their ISVs
> should be ashamed of themselves...
Solaris, for example. IIRC inet_aton isn't in any document which claims
to be a standard.
> however, yours seemed to me an ugly hack, so i have temporarily remove
Martin Johnson wrote:
> Hrvoje Niksic wrote:
> >> 1. Perhaps wget should obey the setting of environment variable
> >> FTP_PASSIVE_MODE ("NO" or "YES")?
>
> > Do other programs obey that variable? Are its semantics defined
> > somewhere?
>
> Yes, FreeBSD's "fetch" command uses that, probably vi
Hrvoje Niksic wrote:
> According to OpenGroup's web site, AI_ADDRCONFIG flag should be of use
> here. Should I be worried that the getaddrinfo man page on my (RHL 9)
> system doesn't mention AI_ADDRCONFIG?
Yes. The end of OpenGroup's man page says:
IEEE Std 1003.1-2001/Cor 1-2002, item XSH
Hrvoje Niksic wrote:
> acknowledge it altogether. The worst thing to do is require the user
> to investigate why the HTML didn't parse, only to discover that Wget
> in fact had the ability to process it, but didn't bother to do so by
> default.
You can have both things, kind of. First you try to
Hrvoje Niksic wrote:
> access to structure elements *looks* like it's accessing an sa_len
> element, whereas in fact it's in fact accessing a union. This is all
> very nice until you try to name a variable "sa_len".
That's why dear standards reserve large chunks of the namespace. Something
or ot
Hrvoje Niksic wrote:
> The whole matter of conversion of "/" to "/index.html" on the file
> system is a hack. But I really don't know how to better represent
> empty trailing file name on the file system.
Another, for now rather limited, hack: on file systems which support some
sort of file attri
Hrvoje Niksic wrote:
> David Fritz <[EMAIL PROTECTED]> writes:
>
> > IIUC, GNU coreutils uses uintmax_t to store large numbers relating to
> > the file system and prints them with something like this:
> >
> >char buf[INT_BUFSIZE_BOUND (uintmax_t)];
> >printf (_("The file is %s octets long.
Jan Minar wrote:
> What's wrong with mbrtowc(3) and friends? The mysterious solution is
> probably to use wprintf(3) instead printf(3). Couple of questions on #c
> on freenode would give you that answer.
Historically, wget source was written in a way which allowed one to
compile it on really ol
Hrvoje Niksic wrote:
> 2) Server messages printed by Wget in normal operation, such as the
>"200 Ok" message. That one is printed just for the "fun factor"
>anyway, we could as well print just the response code. However, I
>don't see a problem with simply filtering out the non-ASCII'
Marcel Partap wrote:
> http://www.rwth-aachen.de/gruenderkolleg/spinoffs/firma.php?id=22&PHPSESSID=7f0dd9f1ff08d9ce3acc2039577c60b1
> That PHPSESSID stuff sux. If I download it again, it will not overwrite
> old with new but make a new one. So I dema.. eeh WE need a command
> switch to kill thos
Hrvoje Niksic wrote:
> Google doesn't show even nearly enough hits when you search for "libtool
> sucks".
Because it's an understatement. :-)
--
.-. .-.Yes, I am an agent of Satan, but my duties are largely
(_ \ / _) ceremonial.
|
|[EMAIL PROTECTED]
Hrvoje Niksic wrote:
> Rahul Joshi <[EMAIL PROTECTED]> writes:
>
> > Does wget have any option/facility to remove the HTML tags of the
> > retrieved pages so that only the text content can be obtained? For
> > example:
> [...]
>
> No. You will need to use something like `lynx -dump' for that
> p
Graham Leggett wrote:
> On Wed, May 2, 2007 9:16 am, Daniel Stenberg wrote:
>
> >> Host: kpic1 is a HTTP/1.1 feature. So this is non-sensical.
> >
> > Some pre-1.1 servers have required this header, I don't see how the 1.0
> > spec
> > forbids it and by using it you can utilize name-based virtual
Micah Cowan wrote:
> AFAIK, _no_ system supports POSIX 100%,
AIX and Solaris have certified POSIX support. That's for the latest,
IEEE Std 1003.1-2001. More systems have certified POSIX support for the
older POSIX release.
OTOH, all POSIX releases have optional parts which don't have to be
imple
Micah Cowan wrote:
> Okay, so there's been a lot of thought in the past, regarding better
> extensibility features for Wget. Things like hooks for adding support
> for traversal of new Content-Types besides text/html, or adding some
> form of JavaScript support, or support for MetaLink. Also, supp
15 matches
Mail list logo
