Hi, I’m getting python comments inside fenced code, which should not be visible, clashing with markdown headers and creating an incorrect display of headers in tagbar, e.g.:

I have placed the following inside my .vimrc, after following through the manual’s integration steps (https://github.com/vimwiki/vimwiki/blob/619f04f89861c58e5a6415a4f83847752928252d/doc/vimwiki.txt#L1988) and vwtags.py:
let g:tagbar_type_vimwiki = {
\ 'ctagstype':'vimwiki'
\ , 'kinds':['h:header']
\ , 'sro':'&&&'
\ , 'kind2scope':{'h':'header'}
\ , 'sort':0
\ , 'ctagsbin':'/Library/Scripts/vwscripts/vwtags.py'
\ , 'ctagsargs':'markdown'
\ }
I’ve tried to alter vwtags.py, in order to omit fenced code blocks. Yet, the result remains the same, once i run :TagbarToggle inside vimwiki.
To no avail, I’ve also tried using markdown2ctags.py, as well as omitting g:tagbar_type_ in .vimrc, all producing the same result.
Q: How can this be fixed?
Hi, I’m getting python comments inside fenced code, which should not be visible, clashing with markdown headers and creating an incorrect display of headers in tagbar, e.g.:
I have placed the following inside my .vimrc, after following through the manual’s integration steps (https://github.com/vimwiki/vimwiki/blob/619f04f89861c58e5a6415a4f83847752928252d/doc/vimwiki.txt#L1988) and vwtags.py:
I’ve tried to alter vwtags.py, in order to omit fenced code blocks. Yet, the result remains the same, once i run :TagbarToggle inside vimwiki.
To no avail, I’ve also tried using markdown2ctags.py, as well as omitting g:tagbar_type_ in .vimrc, all producing the same result.
Q: How can this be fixed?