Jongwook Choi

This can be fixed like https://github.com/wookayin/semshi/commit/11cf4e7738377298efd27d7db406c45115b5a79e

Semshi is doing the expected behavior here and this is why you should avoid `import *` statements. Because semshi analyzes the file rather statically, without other modules/files taken into consideration,...

I don't think semshi is responsible for this basic python syntax. I guess you are using a default built-in syntax file, which is a bit outdated. Use polyglot or python-mode....

It only works in neovim.

You'll need to run `:UpdateRemotePlugins` again.

This project seems no longer maintained, and treesitter functionality is IMHO outside the scope of this plugin, so don't get your hopes too high. Could you elaborate what kind of...

You should set `g:python3_host_prog` properly (in your init.vim). This is an example how you can assign it dynamically: ```vim let g:python3_host_prog = substitute(system("which python3"), '\n\+$', '', '') ``` This will...

This has been bothering me as well. A workaround I'm using is (using vim-plug as plugin manager): ``` :call plug#load('semshi') ``` This reloads the semshi plugin and it just works...

I did a bit more of study and found that any syntax or appearance-related commands would make Semshi broken. Specifically, the list is: - syntax on - set background=XXX -...

Bumping this up with #94! (Actually similar errors can happen somewhere else, such as `self._update_step(self._options.always_update_all_highlights)`, etc.)