You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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
I removed all .vim* dotfiles/folders and could start vim without any flaws (as expected).
I reinstalled this repo.
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.
The text was updated successfully, but these errors were encountered: