Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need help: Scratch installation causes Error in02tlib.vim and fugitive.vim #647

Closed
loeschzwerg opened this issue Jul 16, 2021 · 2 comments
Closed

Comments

@loeschzwerg
Copy link

Since yesterday I receive an error when firing up vim.
I don't actually understand it quite well, so maybe someone could support me.
It doesn't seem to restrict the usage. Vim works like usual, it only shows this message on startup

$ vim
Error detected while processing /home/tn/.vim_runtime/sources_non_forked/tlib/plugin/02tlib.vim:
line   77: E1208: -complete used without -nargsError detected while processing /home/tn/.vim_runtime/sources_non_forked/vim-fugitive/plugin/fugitive.vim:
line  431: E1208: -complete used without -nargsline  432: E1208: -complete used without -nargsline  436: E1208: -complete used without -nargsline  440: E1208: -complete used without -nargsPress ENTER or type command to continue

I removed all .vim* dotfiles/folders and could start vim without any flaws (as expected).
I reinstalled this repo.

git clone --depth=1 https://github.com/amix/vimrc.git ~/.vim_runtime
sh ~/.vim_runtime/install_awesome_vimrc.sh

After that I received the exact same error message (unexpected).

So I guess it might have to do something with this config.

Fedora 34 / zsh (oh-my-zsh)

I couldn't find the error message online, only a fix from 2015 regarding a different error and a note one would not be using vim.

@arewm
Copy link

arewm commented Jul 16, 2021

This looks to be a duplicate of #645. A manual workaround is presented: #645 (comment) (i.e. delete the -complete clause wherever the error is thrown).

@loeschzwerg
Copy link
Author

Thanks @arewm I'm gonna close this now and try the workaround on monday.
I wonder why I couldn't find the issue via complete Error description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants