Closed lgalke closed 7 years ago
Sadly I can’t since I’m on Spacemacs now for a while and @blueyed is doing all the work. 🤷♂️ Which reminds me that I should probably transfer the repo to him…
(Daniel please remove your fork of the repo so I can transfer it to you; there’s no reason for me taking any credit for the work you do.)
So I found the reason here vimtex#645.
When your .vim
is a symlink, it's content (especially pack/
) does get loaded after internal filetype, indent, etc scripts.
Solution: Clone your vim directory directly into ~/.vim
..
@hynek I've deleted my fork now, so you can transfer the ownership.
Transfer initiated. Thanks and good luck! :)
Thanks! :)
(maybe you should rewrite License and Authorship though, it reads really weird now :))
To complete @lgalke answer, another solution is to add this to your .vimrc
:
set runtimepath=$HOME/repos/dotfiles/vim,$VIMRUNTIME
In this case, .vim
can stay a symlink.
Hello @hynek, Unfortunately, your plugin does not work in my recent vim8 setup anymore. Here is a minimal example:
It is installed with vim's native packaging system, located in ~/.vim/pack/*/start
After some investigation, I found out that vims native indent/python.vim gets sourced before the indent file of this plugin (because of vim8s
+packages
) and setsb:did_indent
. I fixed it by changing the guard tob:did_pep8_indent
. I know that this fix is somewhat violating vim conventions but for now, it works for me. Could you think of a cleaner solution to integrate in vim8 packages system?Best Regards, lgalke