Daniel Hahler

I was about to file a new issue, but this seems fitting! :) Sphinx allows for using highlighting with literal code blocks by default (via `highlight_language`), and defaults to "python"...

Cool. I do not have much time myself, and the above works good for me already. Let me know what you have in mind: `g:rst_syntax_sphinx_mode` ? In theory this could...

For reference, here's what jedi-vim does to setup the concealing / syntax highlighting: https://github.com/davidhalter/jedi-vim/blob/master/after/syntax/python.vim Maybe vim-operator-highlight could use `containedin=ALL`? (here: https://github.com/Valloric/vim-operator-highlight/blob/master/plugin/operator_highlight.vim#L72) @oblitum Can you test if that fixes the issue,...

Would be good to have this rebased after https://github.com/vim-jp/vim-vimlparser/pull/146. I did #146 initially since I wanted to see if the changed code here is covered.

close-reopen for codecov. There appears to be an issue with them. Looks ok from https://codecov.io/gh/vim-jp/vim-vimlparser/commit/356460528c14390b6eb7e88f3d1c70afa894d1af - but let's wait for it a bit.

Yeah, I think we should not use universal newlines. Can you tell where in vimlparser this happens?

But the following could be supported: ```vim let cmd_exec = 'python3' execute 'command! -nargs=1 PythonJedi '.cmd_exec.' ' PythonJedi

Is this handled by the scripts to update this automatically? (see https://github.com/vim-jp/vim-vimlparser/issues/171)

:+1: for shipping `monkeypatch_session` as a workaround - often missed it myself.

Yes, adding an augroup fixes this the parsing/execution of VimEnter. But it does not fix the problem at hand here: for the first buffer (or rather when `TPlugin autoclose` gets...