Bug#401000: vim: Vim not handling .gz files anymore
Peter Eckersley
pde at csse.unimelb.edu.au
Mon Dec 4 20:08:07 UTC 2006
On 04/12/06, James Vega <jamessan at debian.org> wrote:
>
> On Wed, Nov 29, 2006 at 04:59:45PM -0800, Peter Eckersley wrote:
> > After a recent upgrade (to version 7+), vim on my system stopped
> decompressing
> > .gz files automatically. This looks a bit like #348661.
>
> If this is the same problem as #348661, then you chose not to accept the
> maintainer version (or perform a merge) of /etc/vim/vimrc when
> upgrading. Running ":set runtimepath?" in vim will likely have
> /usr/share/vim/vim64 (or vim63 depending on what you upgraded from)
> instead of /usr/share/vim/vim70.
You'll probably also have an
> /etc/vim/vimrc.dpkg-new or .dpkg-dist which is the newer maintainer
> version of the file.
Nope, it isn't that -- I think I have the latest /etc/vim/vimrc (no -new or
-dist versions, just -old)
md5sum /etc/vim/vimrc
080bf1170946fa1c181ba69a74522435
My runtime path is pretty weird:
runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim,/usr/share/vim/vimfiles/after,~/.vim/after
I guess that's being set by the old binary that's in /usr/bin/vim
strings /usr/bin/vim | grep vimfiles
~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after
Maybe the install scripts should check for old redirects on /usr/bin/vim and
remove them?
Also, you can check /var/log/dpkg.log to see from which version you
> upgraded.
Very useful to know :). The output of:
cd /var/log ; zgrep vim `ls --sort=time dpkg*`
is at http://www.cs.mu.oz.au/bugs/vim-upgrades.gz
I think it was the 2006-10-11 upgrades that caused the problem.
--
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20061204/0b0f1a7d/attachment.html
More information about the pkg-vim-maintainers
mailing list