ngollan wrote:
Trying to use ":e http://www.ietf.org/rfc/rfc1918.txt"; without elinks causes
vim to try links with the -source parameter; links does not decode the stream, and dumps
a raw binary gzip stream into the buffer, which is at least inconsistent with the
behaviour of elinks.
Using the -dump parameter instead of -source should fix that.
I would appreciate some feedback from folks about this proposed change.
My own linux systems use elinks rather than links. My understanding is
that web pages are typically in ascii, not compressed -- so why would
"raw binary gzip streams" show up when viewing urls -- perhaps this
happens when one is attempting to examine an url pointing to a gzipped
file. In which case, gzip streams wouldn't be the only item (bzip2,
zip, jpg, and numerous other non-ascii files).
With elinks, my man page shows:
-dump [0|1] (default: 0)
Print formatted plain-text versions of given URLs to stdout.
-source [0|1] (default: 0)
Print given URLs in source form to stdout.
I'm inclined not to accept this change. 1) it is, after all, a change,
and 2) setting "g:netrw_http_cmd" allows users to get whatever they want
for handling urls.
Regards,
C Campbell
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
