vim-outdated-plugins
vim-outdated-plugins copied to clipboard
semanser
Defect. Plugin shows that there is 1 plugin to update
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)
Not sure, if this is related, but now I do have Plugins to update: 9, however, If I run :PlugUpdate - nothing is getting updated
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?
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
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
@kopach @pyriand3r Does semanser/vim-outdated-plugins/pull/15 fix the issue for you?
Hi, tested it with the new master branch. No change. Still have Plugins to udpate: 1 on startup. sry
Would you mind posting your plug list exactly as it appears in your vimrc/init.vim?
On Mon, Oct 14, 2019 at 5:24 AM pyriand3r [email protected] wrote:
Hi, tested it with the new master branch. No change. Still have Plugins to udpate: 1 on startup. sry
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/semanser/vim-outdated-plugins/issues/14?email_source=notifications&email_token=AFIVDQSW6TNJZTCHFVSSDILQOQ3GHA5CNFSM4GHY5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBD4MII#issuecomment-541574689, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIVDQUTIUQYYHLGCLT2TXDQOQ3GHANCNFSM4GHY5A2Q .
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
@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.
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.
Great! Hopefully @semanser responds to this PR at some point so we can both point back to the main repo, but for now, please continue to use my fork.
On Wed, Oct 16, 2019 at 3:44 AM pyriand3r [email protected] wrote:
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.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/semanser/vim-outdated-plugins/issues/14?email_source=notifications&email_token=AFIVDQTUD7EWTFLJSKYTC4DQO3A4XA5CNFSM4GHY5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBLPGZA#issuecomment-542569316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIVDQTD3ALVL5P3GDSEEMLQO3A4XANCNFSM4GHY5A2Q .
By the way, if it’s useful to you, I added g:outdated_plugins_trigger_mode, which you can set to a truthy value to trigger :PlugUpdate whenever any plugins are behind. I find auto-update to be much easier than watching for a message, which I’m not always paying attention to, but to each their own.
On Thu, Oct 17, 2019 at 2:07 PM Randy West [email protected] wrote:
Great! Hopefully @semansers responds to this PR at some point so we can both point back to the main repo, but for now, please continue to use my fork.
On Wed, Oct 16, 2019 at 3:44 AM pyriand3r [email protected] wrote:
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.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/semanser/vim-outdated-plugins/issues/14?email_source=notifications&email_token=AFIVDQTUD7EWTFLJSKYTC4DQO3A4XA5CNFSM4GHY5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBLPGZA#issuecomment-542569316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIVDQTD3ALVL5P3GDSEEMLQO3A4XANCNFSM4GHY5A2Q .
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.
@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.
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!