>> So instead, put your changes in .vimrc (and you made the correct changes >> to get dvi->ps->pdf working). > IMHO, it's better to put these changes inside .vim/ftplugin/tex.vim, > such that they will be sourced only when editing a tex file.
I think it depends on the particular changes you want to make. For example, let g:tex_flavor='latex' should go in your .vimrc. Most of the changes mentioned in this thread could definitely go in your personal .vim/ftplugin (or behind an autocommand (block) that masks off the changes for all but TeX files). However, you have to be careful to make that as a rule. For example, if you want to change the way placeholders work, you must put those imaps in your .vimrc as the imaps.vim plugin gets sourced as soon as Vim starts. See: :help remapping-latex-suite-keys :help ls_a_ei for details. Still, some people might not use pathogen and are hesitant to backup their configuration modifications in .vim/ftplugin because they don't want to backup a bunch of other junk... Some people might also just be uncomfortable with .vim/ftplugin (and .vim/after/, etc.) and thus want to keep things in .vimrc. Others just might think debugging is easier when all configuration options are set in one place (and after all, you can setup autocommands in the .vimrc to source other configuration files on demand that are located in other places). --Ted -- Ted Pavlic <t...@tedpavlic.com> ------------------------------------------------------------------------------ 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
