From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: markdown
Date: Tue, 19 Jul 2011 07:10:25 -0700 [thread overview]
Message-ID: <CANenyVPoUaPuMWBhCKf9UJmMOg5O8a6jCh6UJJQ=wJHS8WWkOA@mail.gmail.com> (raw)
In-Reply-To: <4E258F19.1050301@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 884 bytes --]
On Tue, Jul 19, 2011 at 7:05 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Hi Khaled,
>
> I took a look at the lunamark code, and ran it on some (copied) sample. As
> it was much slower than I'd expected from lpeg I messed around a little and
> could bring down the runtime on the sample from 2 sec to 0.1 sec. Anyhow,
> there is room for improvement so I wonder If I should take the code, wrap it
> up a bit, and make a module so that we can directly process markdown in
> context. (Of course we then need to keep an eye on how the original
> develops, if mkdown develops at all.)
>
Markdown, in its official form, does not seem to evolve very much. However,
there are extensions to the original syntax, such as those provided by
Pandoc (including nice new reference functionalities) and also the Python
Markdown processor.
Anyway, this is great news! Can't wait to see it in action :)
[-- Attachment #1.2: Type: text/html, Size: 1163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-19 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 14:05 markdown Hans Hagen
2011-07-19 14:10 ` John Haltiwanger [this message]
2011-07-19 17:08 ` markdown Khaled Hosny
2011-07-19 17:14 ` markdown Hans Hagen
2011-07-19 17:25 ` markdown Wolfgang Schuster
2011-07-20 12:24 ` markdown Hans Hagen
2011-07-20 13:08 ` markdown John Haltiwanger
2011-07-21 19:31 ` markdown Wolfgang Schuster
2011-07-21 20:58 ` markdown Hans Hagen
2011-07-22 15:42 ` markdown Wolfgang Schuster
2011-07-26 10:16 markdown Hans Hagen
[not found] <mailman.2332.1311677701.4231.ntg-context@ntg.nl>
2011-07-26 12:37 ` markdown Vyatcheslav Yatskovsky
2011-07-26 12:43 ` markdown Hans Hagen
2011-07-26 14:35 ` markdown Paul Menzel
[not found] <mailman.2340.1311697264.4231.ntg-context@ntg.nl>
2011-07-27 0:27 ` markdown Vyatcheslav Yatskovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANenyVPoUaPuMWBhCKf9UJmMOg5O8a6jCh6UJJQ=wJHS8WWkOA@mail.gmail.com' \
--to=john.haltiwanger@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).