On Tue, Oct 24, 2006 at 03:29:25PM -0700, Diwaker Gupta wrote:
> I'm using Vim 7.0.122 on Debian Unstable. I can send output of
> :version if needed. I've recently started having problems using
> Align.vim:
>
> Error detected while processing function AlignWrapperStart:
> line 28:
> E117: Unknown function: Align#AlignPush
>
> I've tried installing the script from both vim.sf.net as well as Dr.
> Chip's astro-page. Both of them fail with the same error.
In the future, please give a link, such as
http://mysite.verizon.net/astronaut/vim/vbafiles/Align.vba.gz
> Infact, when I extract the files from the vimball using ':so %', it
> generates weird file names:
>
> AlignMaps.vim?[[[1
> AlignPlugin.vim?[[[1
> cecutil.vim?[[[1
>
> Any ideas? Thanks in advance,
> Diwaker
There are a few problems here. First, it is too easy to miss the
warning
BE SURE TO GET THE LATEST VIMBALL PLUGIN BEFORE ATTEMPTING TO
USE SCRIPTS UPLOADED ON OR AFTER AUG 1, 2006
posted on http://mysite.verizon.net/astronaut/vim/index.html . Ideally,
all links to recent plugins would redirect to a page line
http://mysite.verizon.net/astronaut/vim/newvimball.html?file=Align.vba.gz
and this page would give links to the new version of vimball and the
desired plugin.
Second, the link to the new version of vimball is broken:
http://mysite.verizon.net/astronaut/vim/tarfiles/vimball.vba.gz
This does work:
http://mysite.verizon.net/astronaut/vim/tarfiles/vimball.tar.gz
The point is that the newest version cannot be extracted by the older
version, so it is distributed as a tarball instead of a vimball. You
can also get the new version of vimball from
http://www.vim.org/scripts/script.php?script_id=1502 .
The installation instructions there do not mention that the latest
version should be extracted using tar.
When installing vimball, do it in your $VIMRUNTIME directory. (For
me, this means /usr/local/share/vim/vim70 , and I need to use su or sudo
to install.) There may be an even newer version distributed with vim
7.1 or later, and you do not want this version in your personal runtime
directory to be used when you upgrade.
Third problem. This may have been my fault, but when I installed
the vimball plugin, with
$ cd /usr/local/share/vim/vim70
$ sudo tar xzf path/to/vimball.tar.gz
some of the files had the wrong permissions, so I had to fix it with
$ sudo chmod a+r autoload/vimball.vim doc/pi_vimball.txt
plugin/vimballPlugin.vim
Like you, I had some "wrong" files installed at this point. I
cleaned up with
$ cd ~/.vim
$ rm -i */*[[[*
HTH --Benji Fisher
