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

Defect. Plugin shows that there is 1 plugin to update #14

Open
kopach opened this issue Dec 3, 2018 · 17 comments · May be fixed by #16
Open

Defect. Plugin shows that there is 1 plugin to update #14

kopach opened this issue Dec 3, 2018 · 17 comments · May be fixed by #16
Assignees
Labels
bug Something isn't working

Comments

@kopach
Copy link

kopach commented Dec 3, 2018

The plugin shows, that there is 1 plugin to update however all plugins are up to date. With let g:outdated_plugins_silent_mode = 1 option enabled - no messages is shown (as expected)

@semanser semanser added the bug Something isn't working label Dec 3, 2018
@semanser semanser self-assigned this Dec 3, 2018
@kopach
Copy link
Author

kopach commented Dec 20, 2018

Not sure, if this is related, but now I do have Plugins to update: 9, however, If I run :PlugUpdate - nothing is getting updated

@semanser
Copy link
Owner

It seems like it's a problem with disabled plugins. Currently, vim-outdated-plugins searches for all outdated plugins (even deactivated).

@kopach Can u confirm that u have 9 plugins in your ~/.vim/plugged directory but none of them are active at the moment?

@kopach
Copy link
Author

kopach commented Dec 27, 2018

I've just removed .vim/plugged and reinstalled all the plugins again by :PlugInstall + :PlugUpdate. Now, on vim open - I see again message Plugins to update: 1

@pyriand3r
Copy link

Any updates on this? I have installed vim-outdated this morning and ran into the same problem. I have no disabled plugins, all plugins are up to date, vim-plug is up to date and I get the message Plugins to update: 1

@thisisrandy
Copy link

@kopach @pyriand3r Does /pull/15 fix the issue for you?

@pyriand3r
Copy link

Hi, tested it with the new master branch. No change. Still have Plugins to udpate: 1 on startup. sry

@thisisrandy
Copy link

thisisrandy commented Oct 15, 2019 via email

@thisisrandy
Copy link

Actually, I had a look at the init.vim in your dotfiles repo (assume that’s what you use), and I’m surprised this didn’t fix for you, since you also use coc.nvim at the release branch. I’ll have to look more later

@thisisrandy
Copy link

thisisrandy commented Oct 15, 2019

@pyriand3r, I tried using your init.vim, and I get "All plugins up-to-date" when I change vim-outdated-plugins over to my branch. To be completely clear, you need to change Plug 'semanser/vim-outdated-plugins' to Plug 'thisisrandy/vim-outdated-plugins', then run :PlugClean, followed by :PlugInstall in order to test.

@pyriand3r
Copy link

Ah okay, sry. I updated semansers version and thougth that would be enough. I have changed the Plugin to your repository and can confirm that it is working now. "All plugins up-to-date" ;) sorry for the misunderstanding.

@thisisrandy
Copy link

thisisrandy commented Oct 17, 2019 via email

@thisisrandy
Copy link

thisisrandy commented Oct 17, 2019 via email

@pyriand3r
Copy link

Hehe. Was activated seconds after I have read about it ;)

@KillerCars
Copy link

Using the Semanser version I get the same message, Plugins to update: 1.
If I switch to the improve-performance branch I get Plugins to update: 2.
Using the @thisisrandy fork I get the error AttributeError: module 'vim' has no attribute 'async_call'.
I don't know much about this, but is there some pre-requisite for making vim.async_call(check_for_updates) work?
I have Vim 8.2 installed via Brew on MacOS and +python3 is listed in vim --version.

@thisisrandy
Copy link

thisisrandy commented Jan 19, 2020

@KillerCars, I believe vim.async_call is for neovim only. I would highly recommend neovim, but if you need normal vim for some reason, you won't be able to use the python version of the plugin. According to the neovim site, it can be installed via Brew.

@benwainwright
Copy link

Any update on this? I'm getting the same issue

@thisisrandy
Copy link

If anyone is still following this, I didn't really know what I was doing when I rewrote @semanser's vimscript version, and it turns out I ended up writing something that had the potential to block the neovim plugin manager. I did a rewrite today as a remote (new-style) plugin, which means that the plugin now has practically zero startup cost and will never block the user. I've also made it much clearer that only neovim is supported. Hope you all find it useful!

CyrusYip added a commit to CyrusYip/dotfiles that referenced this issue Jun 3, 2022
Defect. Plugin shows that there is 1 plugin to update #14

semanser/vim-outdated-plugins#14

This reverts commit 965c377.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
6 participants