From c5a7911741850777b699a63ae5b7702e379a5ada Mon Sep 17 00:00:00 2001 From: albert-github Date: Sat, 14 Nov 2015 13:42:31 +0100 Subject: [PATCH] Markdown with @cond and @endcond In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.). Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added. --- src/commentcnv.l | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/commentcnv.l b/src/commentcnv.l index 8762b6aa7f1..f65c0738538 100644 --- a/src/commentcnv.l +++ b/src/commentcnv.l @@ -781,6 +781,7 @@ void replaceComment(int offset); //printf("** Adding start of comment!\n"); if (g_lang!=SrcLangExt_Python && g_lang!=SrcLangExt_VHDL && + g_lang!=SrcLangExt_Markdown && g_lang!=SrcLangExt_Fortran) { ADDCHAR('/'); @@ -800,6 +801,7 @@ void replaceComment(int offset); { if (g_lang!=SrcLangExt_Python && g_lang!=SrcLangExt_VHDL && + g_lang!=SrcLangExt_Markdown && g_lang!=SrcLangExt_Fortran) { ADDCHAR('*');