lyt - simple literate programming tool

	Commit message (Collapse)	Author	Age
*	Tangle: Order fragments correctlyHEAD master	Benjamin Barenblat	2015-02-17
\|
*	Weave: Escape references to LaTeX properly	Benjamin Barenblat	2015-02-13
\|
*	Remove leading spaces and/or one newline from code blocks	Benjamin Barenblat	2015-02-12
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	listings is space-sensitive, so the common idiom <<block name>>= block body @ gets typeset as ⟨block name⟩≡ block body This is ugly, so remove all leading spaces up to the first newline (and that newline itself, if appropriate) in each code block.
*	Get rid of Debug.Trace	Benjamin Barenblat	2015-02-12
\|
*	Rewrite parser, again	Benjamin Barenblat	2015-02-11
\| \| \| \| \| \| \| \| \| \|	Rewrite the parser with an actual grammar this time. It’s a bit ugly in places – use of the 'manyTill'' function is especially nasty and ought to be replaced with more <\|> combinators, as in the 'literateFile' definition. Many thanks to Chelsea Voss <csvoss@mit.edu> for helping me figure out the grammar for this.
*	Send errors to stderr	Benjamin Barenblat	2015-02-11
\|
*	Define command-line interface	Benjamin Barenblat	2015-02-11
\|
*	Write weave	Benjamin Barenblat	2015-02-11
\|
*	Fragment: Give up and use pattern matching	Benjamin Barenblat	2015-02-11
\| \| \| \| \| \|	I’m normally opposed to pattern matching in high-quality apps, but this is so small that I’m unconvinced it’ll be a problem. I can always switch to explicit accessors if things get too coupled.
*	Write tangle	Benjamin Barenblat	2015-02-11
\|
*	Parser: Allow internal chunk references	Benjamin Barenblat	2015-02-11
\|
*	Rewrite parser for cleanliness	Benjamin Barenblat	2015-02-11
\|
*	Parse fragments	Benjamin Barenblat	2015-02-11
\|
*	Initial commit	Benjamin Barenblat	2015-02-11