bug: Not an editor command: UpdateRemotePlugins

[HawkinsT]

Did you check docs and existing issues?

• I have read all the lazy.nvim docs
• I have searched the existing issues of lazy.nvim
• I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)

0.9.0-dev-373+gf1b88ced0

Operating system/version

Arch Linux

Describe the bug

Using build = ":UpdateRemotePlugins" results in a build failed error: Error while parsing command line: E492: Not an editor command: UpdateRemotePlugins. For example:

{
    "wookayin/semshi",
    build = ":UpdateRemotePlugins",
}

will cause this error. Running :UpdateRemotePlugins manually works as expected and the equivalent in packer (run = ":UpdateRemotePlugins") also works fine so I believe this is a bug.

Steps To Reproduce

1. Try to install the following plugin as so:

{
    "wookayin/semshi",
    build = ":UpdateRemotePlugins",
}

2. See the error.

Expected Behavior

No error is reported and UpdateRemotePlugins runs successfully.

Repro

local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({
        "git",
        "clone",
        "--filter=blob:none",
        "https://github.com/folke/lazy.nvim.git",
        "--branch=stable", -- latest stable release
        lazypath,
    })
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
    {
        "wookayin/semshi",
        build = ":UpdateRemotePlugins",
    }
})

[max397574]

perhaps for this the plugin needs to be loaded (setup called)?

[folke]

It's because the rplugin has not been loaded yet when the build gets triggered. Will see how this can be solved

[folke]

@max397574 when building a plugin, the plugin is always loaded (regardless of lazy loading), so that was working as expected already

[LeonHeidelbach]

@folke I get the same issue on the current HEAD 887eb75. If I manually try to run :UpdateRemotePlugins I get "E492: Not an editor command: UpdateRemotePlugins". If I then try to run the command directly like this :call remote#host#UpdateRemotePlugins() I get the error "E121: Undefined variable: g:loaded_remote_plugins". It seems like the plugin is never loaded. Is there some manual setup required to load the rplugin correctly?

Running this command from your commit 666ed7b: :lua vim.cmd([[silent! runtime plugin/rplugin.vim]]) loads the plugin and also registers the :UpdateRemotePlugins user command. Running :UpdateRemotePlugins afterwards properly generates the rplugin.vim file in the data directory. Since the rplugin is never loaded on startup though, plugins like wilder do not work.

[folke]

@LeonHeidelbach did you disable rplugin in lazy's config?

You shouldn't obviously

[LeonHeidelbach]

@folke Oh damn, thank you for the quick hint. I did not disable the plugin myself, but since I am using NvChad and just switched to v.2.0 with Lazy I didn't know that there was a separate option to disable default plugins. This is the corresponding line for anyone who might run into the same problem. I really do not know why this would be disabled by default in NvChad though. I must say the speed improvement compared to my prior Packer setup even without lazy loading most of the plugins atm., is quite remarkable. Great job!

[max397574]

it's disabled by default so it's faster ig 🤷

[LeonHeidelbach]

The speed improvement of this is most likely not even measurable though 😉. It just causes problems like this one 😆.

[kushb30]

@folke Oh damn, thank you for the quick hint. I did not disable the plugin myself, but since I am using NvChad and just switched to v.2.0 with Lazy I didn't know that there was a separate option to disable default plugins. This is the corresponding line for anyone who might run into the same problem. I really do not know why this would be disabled by default in NvChad though. I must say the speed improvement compared to my prior Packer setup even without lazy loading most of the plugins atm., is quite remarkable. Great job!

@LeonHeidelbach i tried removing the line still it is not working