Re: [Vim-latex-devel] help for latex-suite is not installed

[Srinath A. <sr...@fa...>]

On Tue, 12 Oct 2004, Luc Hermitte wrote:

> * On Mon, Oct 11, 2004 at 09:18:51AM +0500, Aditya Mahajan <adi...@al...> wrote:
> > A suggestion to vim-latex team. There are some vim plugins that
> > 'install' the help file the first time they are executed. Is it
> > possible to have the same mechanism with latexsuite.
>
> Note: the "installation" procedure does not need to be as complex as the
> one of several other (ft)plugins -- BTW, some use a non portable way to
> create directories...
>
> As vim-latex uses many different files. Just a plugin that checks the
> timestamps and runs :helptags would be enough. No need to extract the
> help from a vim-script.
>

A few problems I forsee with a plugin which needs to install the help
files automatically:

1. What about distributions of latex-suite which are installed by an
   administrator and the user does not have write permissions into the
   directory where the tags file needs to be generated. For example,
   the debian distro has a way of generating the tags file automatically
   without any further help from the user.

2. How to ensure that the function doesn't run everytime. It would be
   annoying for a function to have to run every time gvim starts up
   although the tags file has already been generated. This has
   a potential workaround: Place the function in a file which removes
   itself after the first time it runs. This is already done in
   ~/vimfiles/ftplugin/tex/brackets.vim.

The first problem is a bit more "interesting" though. I guess something
which checks for write-permissions could be implemented. Also, I don't
forsee doing this myself in the next few weeks at least. If someone else
has a suggestion/patch, please step forward.

-- 
Srinath

NOTE: If you are not subscribed to vim-latex-devel, then further replies
	  to the list will be silently ignored. Please subscribe if you wish to
	  continue the thread, or use

		From: vim...@so...valid
		Reply-To: yo...@em...dress, vim...@li...

      in the header.