-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
Not sure, if this is related, but now I do have |
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 |
I've just removed |
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 |
@kopach @pyriand3r Does /pull/15 fix the issue for you? |
Hi, tested it with the new master branch. No change. Still have |
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 ***@***.***> 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
<#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 |
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 ***@***.***> 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
<#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 ***@***.***> 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 ***@***.***>
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
> <#14?email_source=notifications&email_token=AFIVDQTUD7EWTFLJSKYTC4DQO3A4XA5CNFSM4GHY5A22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBLPGZA#issuecomment-542569316>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFIVDQTD3ALVL5P3GDSEEMLQO3A4XANCNFSM4GHY5A2Q>
> .
>
|
Hehe. Was activated seconds after I have read about it ;) |
Using the Semanser version I get the same message, |
@KillerCars, I believe |
Any update on this? I'm getting the same issue |
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! |
Defect. Plugin shows that there is 1 plugin to update #14 semanser/vim-outdated-plugins#14 This reverts commit 965c377.
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)The text was updated successfully, but these errors were encountered: