Stefan Gojan

Sadly I haven't time either :(

oh sorry, I totally overlooked that one, I use it. `after/ftplugin/javascript.vim`: ```vim setlocal matchpairs=(:),{:},[:], let b:match_words = ']*\%(/\@\|$\):

the command outputs: `]*\%(/\@\|$\):

I removed the other plugins now: ```vim let g:python_host_prog='/home/hoschi/.pyenv/versions/neovim2/bin/python' let g:python3_host_prog = '/home/hoschi/.pyenv/versions/neovim3/bin/python' function! DoRemote(arg) UpdateRemotePlugins endfunction call plug#begin('~/.config/nvim/plugged') "Plug 'lifepillar/vim-solarized8' " https://github.com/lifepillar/vim-solarized8 "Plug 'sheerun/vim-polyglot' " https://github.com/sheerun/vim-polyglot Plug 'andymass/vim-matchup' "...

> I think this should be fixed > ... > I think as @orbisvicis this is more usefull and expected when fixed, see also #116

Opt-in sounds like a good compromise.

@Akin909 no worries ;)

> The first I'm not so sure about (I didn't test on the non-WebGL renderer, so its possible it just isn't hooked up for the WebGL one), Same problem with...

I had no problems with coc to scan the code in the buffer, but didn't tried with native LSP. It needs deeper integration to resolve the location in the yode...

+1