Nvim 0.9.5 still can not register wilder.nvim with UpdateRemotePlugins on Windows

[lee-shun]

nvim version:

NVIM v0.9.5
Build type: RelWithDebInfo
LuaJIT 2.1.1703942320
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe /MD /Zi /O2 /Ob1  -W3 -wd4311 -wd4146 -DUNIT_TESTING -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -D_WIN32_WINNT=0x0602 -DMSWIN -DINCLUDE_GENERATED_DECLARATIONS -ID:/a/neovim/neovim/.deps/usr/include/luajit-2.1 -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/build/src/nvim/auto -ID:/a/neovim/neovim/build/include -ID:/a/neovim/neovim/build/cmake.config -ID:/a/neovim/neovim/src -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include -ID:/a/neovim/neovim/.deps/usr/include

   system vimrc file: "$VIM\sysinit.vim"
  fall-back for $VIM: "C:/Program Files (x86)/nvim/share/nvim"

Run :checkhealth for more info

wilder configuration:

" TODO: need to figure out the nvim python bug
call wilder#setup({'modes': [':', '/', '?']})

if has('python')
    " For Neovim or Vim with yarp
    " For wild#cmdline_pipeline():
    "   'language'   : set to 'python' to use python
    "   'fuzzy'      : 0 - turns off fuzzy matching
    "                : 1 - turns on fuzzy matching
    "                : 2 - partial fuzzy matching (match does not have to begin with the same first letter)
    " For wild#python_search_pipeline():
    "   'pattern'    : can be set to wilder#python_fuzzy_delimiter_pattern() for stricter fuzzy matching
    "   'sorter'     : omit to get results in the order they appear in the buffer
    "   'engine'     : can be set to 're2' for performance, requires pyre2 to be installed
    "                : see :h wilder#python_search() for more details
    call wilder#set_option('pipeline', [
                \   wilder#branch(
                \     wilder#cmdline_pipeline({
                \       'language': 'python',
                \       'fuzzy': 1,
                \     }),
                \     wilder#python_search_pipeline({
                \       'pattern': wilder#python_fuzzy_pattern(),
                \       'sorter': wilder#python_difflib_sorter(),
                \       'engine': 're',
                \     }),
                \   ),
                \ ])
endif

if g:has_popup_win
    let s:highlighters = [
                \ wilder#pcre2_highlighter(),
                \ wilder#basic_highlighter(),
                \ ]

    call wilder#set_option('renderer', wilder#renderer_mux({
                \ ':': wilder#popupmenu_renderer({
                \   'highlighter': s:highlighters,
                \   'left': [
                \   ' ', wilder#popupmenu_devicons(),
                \   ],
                \   'right': [
                \   ' ', wilder#popupmenu_scrollbar(),
                \ ],
                \ }),
                \ '/': wilder#popupmenu_renderer({
                \   'highlighter': s:highlighters,
                \ }),
                \ }))
endif

I got the following error when I pressed /

after using UpdateRemotePlugins, the wilder is still NOT registered.

I also checked the let g:loaded_remote_plugins with :verbose et g:loaded_remote_plugins. And I got:

Cloud you please help me with that?

[fortizc]

I had the exact same issue, but in my case, the problem was a plugin for black (the python formatter). So I just needed to remove Wilder, install black (to fix my issues with that plugin) run UpdateRemotePlugins to register the black plugin, install Wilder again and run UpdateRemotePlugins again to register Wilder.

Please check if you have any other problematic plugin, fix it and then try again

[lee-shun]

Thanks! SO you mean I can use the black to format the widler's python scripts and then use the formatted widler.nvim?

[fortizc]

Thanks! SO you mean I can use the black to format the widler's python scripts and then use the formatted widler.nvim?

No, I just said that in my case the problem was generated by other plugin.

Just check if you don't have any other plugin with problems

[bon-ami]

This behavior same as #203. After :UpdateRemotePlugins, the rplugin manifest file (as pointed in the screenshot in the first comment) still does not contain anything useful, which leads to the failure.
This needs neovim to check as I posted neovim/neovim#30470
And this remote plugin mechanism is being deprecated soon. neovim/neovim#27949
For now, I have to comment out using this plugin.