On Wed, Jul 28, 2010 at 02:55:16AM +0200, Peter Odding wrote: > Gary Johnson wrote: > >I may have found a clue. I started vim much as you did but with > >'verbose' set to 9 and the output saved to a file. > > > > vim -u NONE -U NONE -i NONE -N -V9vimout -c 'let &rtp = $VIMRUNTIME > > | runtime! plugin/**/*.vim | edit http://www.vim.org/' > > > >Before displaying the contents of the URL, Vim displayed this at the > >bottom of the screen: > > > > :!elinks 'http://www.vim.org/' -source > '/tmp/vOjHkf8/0' > > "/tmp/vOjHkf8/0" 412L, 16869C > > /home/garyjohn > > Press ENTER or type command to continue > > > >The log file 'vimout' also contained some commands related to > >elinks. So I wonder if there might be something wrong or just > >different about your installation of elinks. If you don't have > >elinks, netrw might try to use some other program and there might be > >a problem with it. > > > >On this RHEL4 system, "which elinks" returns "/usr/bin/elinks" and > >"elinks -version" returns "ELinks 0.9.2 - Text WWW browser". > > > >Try that and let's see what you get. > > Thanks to your hints I seem to have found the problem. On my system > "elinks" doesn't exist so netrw tries "links", which does exist: > > $ which links > /usr/bin/links > $ man links # calls it links2 > > But with a twist (?): > > $ links http://www.vim.org/ -source | file - > /dev/stdin: gzip compressed data, from Unix
Sounds like links sends "Accept-Encoding: gzip" when it requests the page. You can see a similar difference in "curl -I http://www.vim.org/"; vs. "curl -I -H 'Accept-Encoding: gzip' http://www.vim.org/";. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>
signature.asc
Description: Digital signature
