editor-bootstrap/vim-bootstrap

Error on edit markdown

arthur29 opened this issue · 2 comments

arthur29 commented
  • Vim bootstrap version(number in first line): No version given
  • Operating system: MacOS Catalina
  • Vim/Nvim version: VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 21 2020 04:03:24)
  • Languages: markdown

Description

I writing a new Markdown file and when I add a new code block with the sequence of characters "```", the editor auto-remove the third "`" caracter. I tried to remove markdown as an available language on vim-polyglot and remove conceal thinking that it, but it not solve the problem.

The lines that I add to vimrc file was:

let g:vim_markdown_conceal = 0
let g:vim_markdown_conceal_code_blocks = 0

Please can you help me?

cassiobotaro commented

I tested here using let g:vim_markdown_conceal_code_blocks = 0 and it works!

You can add these two lines in .vimrc.locals and it will be executed before other configurations.

ross commented 
let g:vim_markdown_conceal = 0
let g:vim_markdown_conceal_code_blocks = 0

The above in .vimrc.locals worked for me previously, but on a new laptop with a newly setup vim-boostrap it no longer does. I don't see vim-markdown in the .vim/plugged directory so maybe it has been replaced by a new module?

Regardless set conceallevel=0 does work, but only when run manually once the buffer has been loaded. When it's in my .vimrc.local it doesn't seem to take effect.

Some searching around in the .vim files lead me to indentLine talking about overwriting your concelLevel in its README.md, https://github.com/Yggdroot/indentLine#customization (search for "Change Conceal Behaviour")

Based on that I added the following to my vim file and markdown no longer hides the details, nor does any of the other syntax based concealment/special handling, e.g. json.

let g:indentLine_conceallevel = 0

If you just want to do it for markdown something like the following will probably work:

au FileType markdown let g:indentLine_conceallevel = 0

Not really sure where this should be documented or anything since it doesn't directly have anything to do with vim-bootstrap or anything it mentions in documentation. It does seem that a lot of people use vim-bootstrap and get annoyed by this behavior so perhaps it's something that vim-bootstrap could disable.