fix: don't set conceallevel from syntax plugin #108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that when I load a markdown file in vim, the
vim-json
file automatically runsset conceallevel=2
. There's a few configs which are necessary to reproduce this:let g:markdown_fenced_languages = [ 'json', ... ]
elzr/vim-json
pluginWhen these conditions are met, the markdown plugin will load the
vim-json/syntax/json.vim
script. The problem is that this script does something unusual by also loading the correspondingftplugin
script. Since loading theftplugin
script is the root cause, the fix is to stop loading this script. Because theg:vim_json_syntax_conceal
plugin might be uninitialized now, this guards the references withexists()
expressions. This is the same pattern as used in the builtin json syntax plugin (vim/runtime/syntax/json.vim
).I tested this with:
set conceallevel=2 | let g:vim_json_syntax_conceal = 0
set conceallevel=0 | let g:vim_json_syntax_conceal = 1
Fixes #104