Verifying a vim-latex install with F9 is not the best idea as this relies on your vim having been built with python, and a bib file to be found, as your vimrc shows you are using an additional citation plugin this could also clash with vim-latex's F9 completion. Testing compilation with <Leader>ll (this compiles the saved file on disk rather than in vim) or the F5 or F7 keys to insert environments or commands would be a safer bet, e.g. in a blank tex file typing document then F5 should insert a document template.
vim-latex only loads for files whose filetype is tex (while a plugin manager can enforce this, it is a setting baked into vim-latex) and so ensure :set filetype? returns filetype=tex otherwise vim-latex not being active is expected behaviour.
Otherwise the question is probably whether you are successfully installing the package. While installation instructions are given for manual installation, installation via a plugin manager such as Pathogen or vim-plug is generally recommended.
:set runtimepath? gives some indication of what is getting loaded or with vim-plug :PlugStatus indicates both the status and whether a plugin is loaded.
As your vimrc shows you are already using vim-plug for other plugins it would be advisable to use that. Multiple attempted installations could cause clashes and it would be worth clearing as much as possible. It is probably worth starting with only vim-latex to avoid any clashes, and verifying that a generic plugin (e.g. vim-airline) with no potential overlap can be correctly installed.
Best Answer
As
gvimis justvim“in gtk-window”, I will usevimfor convenience.When you installed
vimvia the packagemanager, it should have gotten its own directory under/etcwith (at least one) templatevimrc./etc/vim/vimrc/etcis usually the place, where configuration-files are stored that apply to the whole system and will be used as fallback, when a user has not defined his own.Your personalized configuration-file should reside below your homedirectory. So, usually, it suffices to just have
/home/my_home/vimrc.It is always a good idea to copy the configuration-file from
/etc/vimand change that as needed. If you so far used vim without a personalized vimrc, then it loaded the/etc/vim/vimrcand you might notice a different behaviour when you start with an empty vimrc.I would recommend to use the hidden directory for vim, in which you can store all vim-related configurations,
i.e.
/home/my_home/.vim/vimrcand plugins, such as the latex-suite.
As for the latex-plugin:
When decompressing the archive, you might only get the following directory:
~/.vim/vim-latex-1.8.23But what you need, is to have that directories contents to be directly under
~/.vim.For example:
~/.vim/vim-latex-1.8.23/latextags→
~/.vim/latextagsSo, the plugin (and its documentation) expects a certain order in the directory-tree, without which, the plugin will not be able to function.
I encountered the same problem at first and finally found this solution. I hope that this can still be of some help.