Semshi/Wilder conflict

[mjbrowns]

So I love the Wilder popup etc, but I really am not thrilled with the python syntax highlighting. I'm using neovim with packer, and have both wilder and semshi set up via lua.

When I fire up neovim to edit a python file I get this:

remote/host: python3 host registered plugins ['semshi', 'wilder'] remote/host: generated rplugin manifest: /home/mbrown/.local/share/nvim/rplugin.vim

I've been reading through stuff all morning and have no idea how to resolve this. I'd like to turn off the wilder syntax highlighter but either I'm clueless or I can't find it in the documentation other than some obscure references to python that don't seem to have anything to do with highlighting.

[wookayin]

This is normal. Both of semshi and wilder can be registered to rplugin manifest. What's "the problem" you're running into?

[mjbrowns]

Hmm. Okay, well...I guess then if that's normal, I'd have to ask if there's a way to suppress the notice I get every time I edit a python module that announces the two registrations. I'm not surprised it would tell me the first time but every time is really annoying.

[wookayin]

:UpdateRemotePlugins should be called only once as a part of build or installing plugins (after updating or installing plugins), not on normal command/keymap use.

[mjbrowns]

Ok. So, taking your very insightful comments, I now have things working properly. It seems that my issue really was the question of how to correctly configure this using the packer plugin manager.

I suggest adding an entry in the README.md on installation with packer.

Based on what I have so far, I suggest:

Add to your plugins.lua (or whatever file you use to install your plugins):

use {'numirias/semshi', ft = 'python'} 

Then, ignoring a variety of nvim startup errors:

1. Run PackerSync (Or PackerInstall)
2. Run UpdateRemotePlugins
   • Important! Must be done while Semshi is loaded; since it's lazy loaded you need to edit a python file to properly UpdateRemotePlugins!

Restart nvim and profit!

[mjbrowns]

Consider this closed.

[wookayin]

See also #184 #109, etc. Unfortunately this repository is abandoned at the moment, and I am not a maintainer of this repo, so I can't add the user guide to README. Please close this issue from your end, thanks.