> Vim help doesn't explain the syntax of every kind of file you might > edit with it. IIUC, by putting text between grave accents in Markdown > `like this` you make it appear in monospace: for instance in Github > comments about Vim problems, this marks inline stuff that would be > typed literally in Vim. (To make a block stand out you put three such > characters above and below it.) > > OTOH manpages often use a grave accent as an opening quote and an > apostrophe as a closing quote, which is one place where unpaired, or > differently paired, such characters might be found (and unwittingly > got from, by copying and pasting).
this solved some previous problems with my markdown files as well, when pandoc printed some lines in monotype -- now I know the reason. I only use the basic set of markdown as described on the daringfireball site. there code is tagged by four spaces, one tab or a <code> tag. the vim syntax coloring works on the extensive md-set, where other characters can be used as formatting tag. using this extensive set brings more formatting options as well. -- a bit OT, but probably useful for other vimmers here... cheers, //meine -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
