[Vim-latex-devel] system-local: 2 problems

[Mikolaj M. <mi...@wp...>]

But these features are not complete. It doesn't break
any existing functionality but is not ready yet.

There are still unresolved
problems:

1. main.vim

" This line seems to be necessary to source our compiler/tex.vim file.  " 
The
" docs are unclear why this needs to be done even though this file is " the 
first
" compiler plugin in 'runtimepath'.
runtime compiler/tex.vim

But with system installation this may will source local version of
compiler. Maybe something like

let lscompilerpath = fnamemodify(s:path, ":p:h")
exe 'source '.lscompilerpath.'tex.vim'

Or we could entirely get rid of compiler/tex.vim, put its contents in
latex-suite/compiler.tex and avoid sourcing of compiler/tex.vim by
including if | endif into main.vim.

2. installation: Makefile

Because I would like to make it more like regular programs Makefile
needs "make install", "make uninstall". But here is problem:

Vim is installed in very various ways. Eg. Mdk don't follow Vim FHS and
there is no place for vimfiles (or vim-scripts as in Debian policy)
dirs.

I am playing now with vim.spec for Mdk and will try to convince
maintainers to follow Vim FHS and even better Debian Vim scripts policy.
With two major distributions following this guidelines it would be
easier to change other.

Maybe we could ask Bram to include vim-scripts directory as an official
directory in Vim FHS? With support in official vim-docs we would have
another point.

In meantime we could offer install.sh script. It could give nice dialogs
with possible choices and explanations about them:

~/.vim - local installation
/usr/local/share/vim/vimfiles  - system wide installation with locally
	build Vim
/usr/share/vim - Vim from package in distro not following Vim FHS
/usr/share/vim/vimfiles - Vim from package in distro which follows Vim
	FHS
/usr/share/vim/vim-scripts - Vim from package in distro which follows
	Debian Vim scripts policy

Of course it could be automated (eg. checking `which vim` could 
answer where Vim is installed and give proper default, maybe check for
`uname -a`).

Such script could allow also for basic preconfiguration of texrc
(default target, latex flavour).

 http://yacoob.dnsalias.net/sakwa/vim-policy.txt

 m.