You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have run into a very strange issue. I am using the exact same init.vim file on my local Mac and a remote server which runs ubuntu. Semshi loads just fine on Mac but runs into this error on Ubuntu.
Error detected while processing function <SNR>17_filetype_changed: line 4: E492: Not an editor command: Semshi enable
I suspect that this error indicates that Semshi is not loaded correctly? I tried to delete other syntax related lines in the init.vim file. At last, I made my init.nvim file looks like this:
Figured it is because I have not run UpdateRemotePlugins!
Reacted by Flyingtime, Vladyslav Krylasov, Marijan Smetko, Landon, Kartikeya Pande, Felix Woolford, Cheikh Tidjane Konteye, Randy Creasi, Eduardo Ferreira, Jonas I. Liechti and 6 more
What does ~/.local/share/nvim/rplugin.vim read for you (or any other similar path that reads from :UpdateRemotePlugins? What output does :UpdateRemotePlugins give you? What is the output of /home/gordonrust/anaconda3/bin/python -c "import pynvim; print(pynvim)" ?
Some more context :
I reinstalled the plugin using PlugInstall from within nvim(was earlier installing it from vim) and after that i am getting the error as shown in the attached image
Sorry for kind of a spam: But just want to say the issue seems resolved for now. Presently the output is
`cat ~/.local/share/nvim/rplugin.vim (base)
" perl plugins
and the issue seems to be gone. And this happened after started a new instance of neovim-qt. Earlier, UpdateRemotePlugins did not seem to help as you can see from the content of my ~/.local/share/nvim/rplugin.vim file earlier. This seems a bit random to me. In one of my earlier attempts, the editor recognized Semsi as an editor command but gave a pyinv unknown function semshi#buffer_attach error on doing Semshi enable manually. But since then, uptil just now, anytime I had opened a new instance of nvim_qt Semshi itself was not even a recognized editor command.
@wookayin Btw, in all these attemts I am using your particular fork Plug 'wookayin/semshi', { 'do': ':UpdateRemotePlugins' }
Again, sorry for a longish post, but there seems to be someting amiss, and I am just trying to help.
To fix this on my end, using python3.11 installed via linuxbrew, I first uninstalled both neovim and pynvim using pip:
pip3.11 uninstall neovim
pip3.11 uninstall pynvim
Then, I reinstalled only pynvim:
pip3.11 install pynvim
Then, I added the following to my init.lua:
-- in vimscript, this would be let g:python3_host_prog = '/home/linuxbrew/.linuxbrew/bin/python3.11'vim.g.python3_host_prog='/home/linuxbrew/.linuxbrew/bin/python3.11'
Then, and only then, did I finally get the :UpdateRemotePlugins in neovim command mode to work for me.
Activity
huyiqun commentedon Mar 31, 2020
Figured it is because I have not run
UpdateRemotePlugins!snevs commentedon May 6, 2020
I have the same issue. UpdateRemotePlugins doesn't work either
matan129 commentedon May 1, 2022
Same happens to me. nvim 0.7.0
lyskai commentedon May 26, 2022
UpdateRemotePlugins doesn't work for me. Below step helps resolve in my side.
alipirpiran commentedon Sep 5, 2022
My problem was solved by installing
pynvimGlobally instead of Locally.I used this command:
A regular
pip install pynvim --upgradewill try to use your own home directory. The -H instructs it to use the system's home directory.wookayin commentedon Nov 1, 2022
pynvim must be installed under the python that you are using for
g:python3_host_prog. It doesn't matter whether it is installed locally or globally.Don't forget you can use the following cmd to see where it is installed -- if it resolves to a strange installation, you should remove it:
gordonrust commentedon Dec 23, 2022
Still getting the 'Not an editor command :Semshi enable' :(
This is my nvim:checkhealth
coc: health#coc#check
nvim: health#nvim#check
Configuration
Performance
Remote Plugins
terminal
provider: health#provider#check
Clipboard (optional)
Python 3 provider (optional)
Python virtualenv
Ruby provider (optional)
rubyandgemmust be in $PATH.rubyandgemcommands work.Node.js provider (optional)
let g:loaded_node_provider = 0to your init.vimPerl provider (optional)
let g:loaded_perl_provider = 0to your init.vimvim.lsp: require("vim.lsp.health").check()
vim.treesitter: require("vim.treesitter.health").check()
wookayin commentedon Dec 23, 2022
What does
~/.local/share/nvim/rplugin.vimread for you (or any other similar path that reads from:UpdateRemotePlugins? What output does:UpdateRemotePluginsgive you? What is the output of/home/gordonrust/anaconda3/bin/python -c "import pynvim; print(pynvim)"?gordonrust commentedon Dec 24, 2022
Thanks for the quick response !!
cat ~/.local/share/nvim/rplugin.vim`" perl plugins
" node plugins
" python3 plugins
" ruby plugins
" python plugins
`
On doing :UpdateRemotePlugins I get
remote/host: generated rplugin manifest: /home/gordonrust/.local/share/nvim/rplugin.vim/home/gordonrust/anaconda3/bin/python -c "import pynvim; print(pynvim)"gives<module 'pynvim' from '/home/gordonrust/anaconda3/lib/python3.9/site-packages/pynvim/__init__.py'>gordonrust commentedon Dec 24, 2022
Some more context :
I reinstalled the plugin using PlugInstall from within nvim(was earlier installing it from vim) and after that i am getting the error as shown in the attached image
gordonrust commentedon Dec 24, 2022
Sorry for kind of a spam: But just want to say the issue seems resolved for now. Presently the output is
`cat ~/.local/share/nvim/rplugin.vim (base)
" perl plugins
" node plugins
" python3 plugins
call remote#host#RegisterPlugin('python3', '/home/gordonrust/.vim/plugged/semshi/rplugin/python3/semshi', [
\ {'sync': v:true, 'name': 'SemshiInternalEval', 'type': 'function', 'opts': {}},
\ {'sync': v:true, 'name': 'Semshi', 'type': 'command', 'opts': {'complete': 'customlist,SemshiComplete', 'nargs': ''}},
\ {'sync': v:true, 'name': 'SemshiBufEnter', 'type': 'function', 'opts': {}},
\ {'sync': v:true, 'name': 'SemshiBufLeave', 'type': 'function', 'opts': {}},
\ {'sync': v:true, 'name': 'SemshiBufWipeout', 'type': 'function', 'opts': {}},
\ {'sync': v:false, 'name': 'SemshiCursorMoved', 'type': 'function', 'opts': {}},
\ {'sync': v:false, 'name': 'SemshiTextChanged', 'type': 'function', 'opts': {}},
\ {'sync': v:true, 'name': 'VimLeave', 'type': 'autocmd', 'opts': {'pattern': ''}},
\ {'sync': v:false, 'name': 'SemshiVimResized', 'type': 'function', 'opts': {}},
\ {'sync': v:true, 'name': 'SemshiComplete', 'type': 'function', 'opts': {}},
\ ])
" ruby plugins
" python plugins
`
and the issue seems to be gone. And this happened after started a new instance of neovim-qt. Earlier, UpdateRemotePlugins did not seem to help as you can see from the content of my
~/.local/share/nvim/rplugin.vimfile earlier. This seems a bit random to me. In one of my earlier attempts, the editor recognizedSemsias an editor command but gave apyinv unknown function semshi#buffer_attacherror on doingSemshi enablemanually. But since then, uptil just now, anytime I had opened a new instance of nvim_qtSemshiitself was not even a recognized editor command.@wookayin Btw, in all these attemts I am using your particular fork
Plug 'wookayin/semshi', { 'do': ':UpdateRemotePlugins' }Again, sorry for a longish post, but there seems to be someting amiss, and I am just trying to help.
jessebot commentedon Jan 2, 2023
To fix this on my end, using python3.11 installed via linuxbrew, I first uninstalled both
neovimandpynvimusing pip:Then, I reinstalled only pynvim:
Then, I added the following to my
init.lua:Then, and only then, did I finally get the
:UpdateRemotePluginsin neovim command mode to work for me.Hope this helps and good luck out there!
feat: show more informative errors when rplugins were not registered