You are not logged in.
Pages: 1
Topic closed
I updated gvim and vim-runtime from 7.4.1529 to 7.4.1584 today. Now, opening a .tex file results in a ton of errors:
The version of vim-latexsuite is 20141116-2. Other vim-plugins seem to work.
Error detected while processing /usr/share/vim/vimfiles/ftplugin/latex-suite/texrc:
line 60:
E116: Invalid arguments for function <SNR>35_SafeLet
line 64:
E116: Invalid arguments for function <SNR>35_SafeLet
[...]
line 18:
E121: Undefined variable: g:Tex_MainMenuLocation
E15: Invalid expression: g:Tex_MainMenuLocation
line 22:
E121: Undefined variable: g:Tex_MainMenuLocation
E15: Invalid expression: g:Tex_MainMenuLocation.'.20 '.s:mainmenuname.'&Templates.'
Offline
I upgraded vim and vim-runtime from 7.4.1529-1 to 7.4.1584-1. Looking at the package history, there are only two commits, and they merely upgrade the version of vim. Etckeeper verifies no global configuration changed.
Now, if I try to run detectindent's :DetectIndent function, I get the error "E116: Invalid arguments for function <SNR>25_DetectIndent". My search has lead to a variety of causes for other plugins, from duplicate plugins to comments in the vimrc while using an old version of vundle. None of these have gotten me very far in diagnosing the issue.
Downgrading back to 7.4.1529 fixes the issue, so it's definitely something contained within the package that triggers it.
Here is my vimrc; it's fairly short. All bundles are up-to-date.
I'm having difficulty in just figuring out whether this is a detectindent problem, or an Arch packaging problem, or an upstream vim problem; if anyone can help me with that part of things, I'd greatly appreciate it.
Offline
From what I can tell, you need to report this to detectindent's author.
Offline
I have the same issue, so I installed vim-latexsuite-git from AUR, version 1:0.r844.0f1230e-1, but I still get the same errors.
Offline
I also have this issue (both vim-latexsuite and vim-latexsuite-git).
I also tried install via Vundle (Plugin 'vim-scripts/LaTeX-Suite-aka-Vim-LaTeX'), and I got the error "remoteOpen.vim command already exists." I don't whether this is related, and I'm not sure how to trouble shoot this (e.g. find out what other package has "remoteOpen.vim").
Offline
There's a few plugins that have broke with the latest vim patch. For now maybe downgrade to the last version of vim and vim-runtime until a patch to fix this patch comes out
Offline
It's also a problem for vim-tmux-navigator, and vim-latexsuite. It sounds like a Arch packaging problem to me..
Offline
I think this is an upstream bug fixed with vim patch #1589.
Offline
I just pushed a new upstream version 7.4.1639 to [testing]. Could you please check if it makes any difference for you?
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
I just pushed a new upstream version 7.4.1639 to [testing]. Could you please check if it makes any difference for you?
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
Mod note: Merged similar threads.
Offline
I just pushed a new upstream version 7.4.1639 to [testing]. Could you please check if it makes any difference for you?
This seems to have fixed the problem for me. Thanks!
Offline
I can confirm that vim (and vim-runtime) 7.4.1639 from [testing] also solve this problem for me.
Offline
I can also confirm that the vim 7.4.1639 packages from testing fix my particular case, thanks!
Offline
There is no need to keep confirming it works...
Closing
Offline
Pages: 1
Topic closed