<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 16 Jul 2016, at 22:35, Stefan Daschek wrote:</p>
<p dir="auto"></p></div>
<div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir="auto">Maybe we could introduce something like |TM_MARKDOWN_PREPROCESSOR| into the existing preview commands? With the idea that as long as this is not set (the default) it does nothing, but if it is set the document gets piped through this first before being processed further.
</div></blockquote></div>
<div style="white-space:normal">
<p dir="auto">This sounds fine to me, however, this should probably be a list.</p>
<p dir="auto">So your bundle would contain:</p>
<pre style="background-color:#F7F7F7; border-radius:5px 5px 5px 5px; margin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; padding:5px" bgcolor="#F7F7F7"><code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0" bgcolor="#F7F7F7">{ shellVariables = (
{ name = 'TM_MARKDOWN_FILTER';
value = '$TM_BUNDLE_SUPPORT/strip-frontmatter:$TM_MARKDOWN_FILTER';
},
);
}
</code></pre>
<p dir="auto">And the preview command would have to do a “split” and run each (non-empty) filter.</p>
<p dir="auto">This could be exploited by users as well, for example I could set <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">TM_MARKDOWN_FILTER</code> to something that generates table-of-contents or enumerate the headings etc.</p>
</div>
</div>
</body>
</html>