> http://www.vim.org/scripts/script.php?script_id=2332

I don't see where pathogen's document is on the above page.

> pathogen will put each bundled plugin into your runtimepath. After that:
>
> Use :Helptags to run :helptags on every doc/ directory in your
> 'runtimepath'.

help :Helptags leads me to :helptags. Where is :Helptags documented?

> Works for me.

:Helptags works for me, too. Thanks!

> That's fine, but it does not justify the extra work it would take to
> convert the Vim-LaTeX page into a gh-pages branch and publicize the
> change in hosting site. So there is significant cost to a conversion and
> very little benefit. Even at a low cost, the latex-suite is primarily in
> maintenance mode at this stage in its life. Without a dedicated batch of
> new developers who are willing to stick it out for the long run, there's
> no way a conversion to a new hosting site could happen. Just switching
> LaTeX-suite from SVN to git took a great deal of effort because it was
> clear that if there were any problems with the conversion that did not
> immediately show up, there might not be devs around to fix them.

I get your point. So the real point is that the effort that takes to migrate.

> You get syntax highlighting for free. It comes with vim. Notice that
> there is no "syntax" directory in vim-latex. Without LaTeX suite, you
> would get the same highlighting so long as your file type was set correctly.

Never check the syntax highlight file. Just checked the indentation file.

> As you can see on the list, most of the active LaTeX-suite users use the
> extended features, like completion, key mappings, smart compilation,
> forward and reverse searching, and the TeX-specific code folding. These
> are features that come in handy when composing very large documents
> (articles, reports, and books) with many parts distributed over many
> files, much like a modern-day program in Java. Those who use LaTeX for
> relatively small projects are usually satisfied with the basic support
> that comes built into distributions of Vim. So that's why the default
> feature set is how it is and why there is not more direct documentation
> for how to turn it off (because for most people, those instructions
> would simply be "uninstall LaTeX suite").

This makes sense for frequent latex users. For me, I only use it
occasionally when I need to write some papers. For my everyday
documents, I use pandoc. Long time ago, before I knew pandoc, I used
to learn the short cuts in vim-latex-plugin. But since I don't use
them everyday, I quickly forgot them. And it doesn't make sense for me
to relearn them unless I am going to use vim-latex-plugin everyday
from now, which is not going to be the case.

So your assumption of frequenter latex users may not always apply. I
think that there should other occasional latex users like me.
Therefore, it is making sense to just add one or two sentence for
describing how to just enable indentation in the initial installation
page.

-- 
Regards,
Peng

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to