Bug 1982290 - "E1208: -complete used without -nargsline" with vim-enhanced-8.2.3154-1.fc34.x86_64
Summary: "E1208: -complete used without -nargsline" with vim-enhanced-8.2.3154-1.fc34....
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim-fugitive
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-14 15:59 UTC by Pavel Raiskup
Modified: 2021-07-15 07:38 UTC (History)
2 users (show)

Fixed In Version: vim-fugitive-3.3^1.4cdeff8-1.fc34
Clone Of:
Environment:
Last Closed: 2021-07-15 03:40:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pavel Raiskup 2021-07-14 15:59:57 UTC
This is a ubiquitous welcome message from vim/gvim now, when I updated
the vim to the given number:

Error detected while processing /usr/share/vim/vimfiles/plugin/fugitive.vim:
line  527: E1208: -complete used without -nargs
line  528: E1208: -complete used without -nargs
line  532: E1208: -complete used without -nargs
line  536: E1208: -complete used without -nargs
Press ENTER or type command to continue

Seems like new vim dislikes -nargs=0 there.

Comment 1 Carl George 🤠 2021-07-15 03:40:09 UTC
I found the upstream issue [0] for this.  It's fixed by this commit [1], and the package has already been updated to a snapshot of that commit for other reasons [2].  It was just now pushed to stable, but if you don't want to wait for mirror propagation you can grab it right now by running:

    dnf --enablerepo updates-testing update vim-fugitive


[0] https://github.com/tpope/vim-fugitive/issues/1791
[1] https://github.com/tpope/vim-fugitive/commit/4cdeff8c33ec2fe0686324bf1846ce158c452754
[2] https://bodhi.fedoraproject.org/updates/FEDORA-2021-f15c16ee20

Comment 2 Pavel Raiskup 2021-07-15 07:38:42 UTC
Ah, I missed there's the Bodhi update.  Thank you.


Note You need to log in before you can comment on or make changes to this bug.