Date: Wed, 26 Apr 2017 03:11:27 +0000 From: "Thomas Mueller" <mueller6722@twc.com> To: freebsd-ports@freebsd.org Subject: Re: Downloading with lynx or w3m, how to download as is, without gratuitous gzip Message-ID: <2E.83.09002.DFF00095@dnvrco-omsmta01> References: <32.A2.09002.B158DF85@dnvrco-omsmta01> <20170424155658.5e5abbf4@asd2> <69.B4.29375.516BDF85@dnvrco-omsmta02> <86inls4w0p.wl-herbert@mailbox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Thomas Mueller skrev: > > Documentation on Lynx and w3m are awful hard to find! > > I couldn't find anything on auto_uncompress or anything else that might be put in ~/.w3m/config. > > If the file on the server is already compressed, for instance a tarball, then I want to download it that way. > > But a browser/downloader has no proper business compressing a file to be downloaded. > For w3m you can set accept_encoding. Default is > accept_encoding gzip, compress, bzip, bzip2, deflate > Try to remove gz, bzip, bzip2 or set it to "". > If you think this is a bug you should report it upstream: > https://github.com/tats/w3m > Herbert I looked through w3m documentation and found nothing on accept_encoding. Their website suggests that w3m is more of a pager than a web browser. Elvis (enhanced vi clone) is/was also a rudimentary text-mode web browser. I don't install w3m explicitly, only if it is pulled in by the ports system as a dependency. Maybe I will take the same approach regarding lynx? I intend to check a NetBSD installation with lynx to see if that misbehaves the same way regarding gratuitous, unwanted gzip compression of downloads. I haven't used links in some time; remember a build on FreeBSD took six hours, but that was with DirectFB on a computer with 256 MB RAM. I think I need to email dickey@invisible-island.net . Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E.83.09002.DFF00095>