Stefan Otte

Thanks @f1se4. I assume you're using the non-figlet version? @PhilRunninger introduced the markers (tr, h1, etc.) to, well, mark a given line and assign/[link](http://vimdoc.sourceforge.net/htmldoc/syntax.html#:highlight-link) a normal syntax element to the...

@PhilRunninger thanks, that is super helpful! I'm using https://github.com/plasticboy/vim-markdown, not `tpope/markdown-vim` (but I did in the past). I just tested with tpope's version and it looks much better: Raw md:...

Another try with no specific md plugin installed...and it woks :) fooo... 

@chris542 @rohitvvv @tkachuk-labs - What is your vim version? - What markdown plugin are you using (if any)? - What are your settings for the markdown plugin?

Hey @chris542, thanks for reporting! I haven't used https://github.com/gabrielelana/vim-markdown, but it actually looks quite nice. My guess is that the ft detection somehow collides. I don't have the bandwidth to...

@laoshaw thanks for reporting! I was looking into other issues and can confirm that code block are not syntax highlighted. Please provide a md snippet which contains an example in...

Note so self: maybe related to this: https://github.com/sotte/presenting.vim/commit/6d87e549fb0bd00db908f501c7b4bff7436daa05

Haha, the `#include` is interpreted as a heading and creates a new slide :) The snippet you posted creates 4 slides, not 2 as one would expect. Fixing the separator...

@laoshaw just to have a semi working version this would be the regex for the slid separator: ```vim # ftplugin/markdown.vim let b:presenting_slide_separator_default = '\v(^|\n)\ze#{1,2} ' ``` You should be able...

The bars are there on purpose, fencing off the code > ideally should not be visible. That is/should be the case if it works.