Allan Odgaard wrote:
On 20 Apr 2008, at 00:28, Sherwood Botsford wrote:
[...]
Suppose that markdown was clever enough to reference an external
file (in .markdownrc of course) for the resolution of LABEL.
Here’s a simple shell script to convert all markdown to HTML and using a
shared
On 20 Apr 2008, at 07:11, Sherwood Botsford wrote:
Hmm. Ok, I think I could to it this way in Template Toolkit:
snip
Downside is then that Markdown has to process every reference
which if you have a few thousand will be time consuming.
(I have an INSERT text at one point that jsut in
Pandoc concatenates input from all files specified on the command
line. So you can just do:
pandoc myfile.txt refs.txt myfile.html
Seems to me that this would be a reasonable default behavior for
Markdown.pl as well, but it doesn't seem to work that way now.
John
+++ Sherwood Botsford
You could do something like:
cat myfile.txt refs.txt | MultiMarkdown.pl myfile.html
F-
On Apr 20, 2008, at 10:40 AM, John MacFarlane wrote:
Pandoc concatenates input from all files specified on the command
line. So you can just do:
pandoc myfile.txt refs.txt myfile.html
Seems
Fletcher T. Penney wrote:
You could do something like:
cat myfile.txt refs.txt | MultiMarkdown.pl myfile.html
F-
On Apr 20, 2008, at 10:40 AM, John MacFarlane wrote:
Pandoc concatenates input from all files specified on the command
line. So you can just do:
pandoc myfile.txt
On Sun, Apr 20, 2008 at 1:25 PM, Sherwood Botsford [EMAIL PROTECTED] wrote:
Umm. Pointers to Markdown implementations with support for extensions?
[Python-Markdown][1] has an [extension api][2]. Interestingly my
[Abbreviation Extension][3] for Python-Markdown does something similar
for
