<br><div><span class="gmail_quote">On 04/12/06, <b class="gmail_sendername">James Vega</b> <<a href="mailto:jamessan@debian.org">jamessan@debian.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Nov 29, 2006 at 04:59:45PM -0800, Peter Eckersley wrote:<br>> After a recent upgrade (to version 7+), vim on my system stopped decompressing<br>> .gz files automatically. This looks a bit like #348661.<br><br>
If this is the same problem as #348661, then you chose not to accept the<br>maintainer version (or perform a merge) of /etc/vim/vimrc when<br>upgrading. Running ":set runtimepath?" in vim will likely have<br>/usr/share/vim/vim64 (or vim63 depending on what you upgraded from)
<br>instead of /usr/share/vim/vim70. </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You'll probably also have an<br>/etc/vim/vimrc.dpkg-new or .dpkg-dist which is the newer maintainer
<br>version of the file.</blockquote><div><br>Nope, it isn't that -- I think I have the latest /etc/vim/vimrc (no -new or -dist versions, just -old)<br><br>md5sum /etc/vim/vimrc<br>080bf1170946fa1c181ba69a74522435<br><br>
My runtime path is pretty weird: <br><br>runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim,/usr/share/vim/vimfiles/after,~/.vim/after<br> </div>I guess that's being set by the old binary that's in /usr/bin/vim<br>
<br> strings /usr/bin/vim | grep vimfiles<br>~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after<br><br>Maybe the install scripts should check for old redirects on /usr/bin/vim and remove them?<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, you can check /var/log/dpkg.log to see from which version you upgraded.</blockquote><div><br>Very useful to know :). The output of:<br><br>cd /var/log ; zgrep vim `ls --sort=time dpkg*`<br><br>is at <a href="http://www.cs.mu.oz.au/bugs/vim-upgrades.gz">
http://www.cs.mu.oz.au/bugs/vim-upgrades.gz</a><br><br>I think it was the 2006-10-11 upgrades that caused the problem.<br> </div></div>-- <br>Peter