haddock.git - Haddock with an org backend (haddorg).

	Commit message (Collapse)	Author	Age	Files	Lines
*	Turn a source code comment into specs	Simon Hengel	2014-02-22	1	-2/+0
\|
*	Strip a single leading space from bird tracks (#201)	Niklas Haas	2014-02-22	1	-1/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This makes bird tracks in the form > foo > bar > bat parse as if they had been written as >foo >bar >bat ie. without the leading whitespace in front of every line. Ideally we also want to look into how leading whitespace affects code blocks written using the @ @ syntax, which are currently unaffected by this patch.
*	Fix @ code blocks	Mateusz Kowalczyk	2014-01-30	1	-0/+1
\| \| \| \| \| \|	In cases where we had some horizontal space before the closing ‘@’, the parser would not accept the block as a code block and we'd get ugly output.
*	Allow escaping in URLs and pictures.	Mateusz Kowalczyk	2014-01-12	1	-4/+15
\| \| \| \| \| \| \| \| \|	Some tests were moved under parseString as they weren't about paragraph level markup. Conflicts: src/Haddock/Parser.hs test/Haddock/ParserSpec.hs
*	Allow for nesting of paragraphs under lists.	Mateusz Kowalczyk	2014-01-12	1	-26/+84
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The nesting rules are similar to Markdown's with the exception that we can not simply indent the first line of a hard wrapped indented paragraph and have it treated as if it was fully indented. The reason is differences in markup as some of our constructs care about whitespace while others just swallow everything up so it's just a lot easier to not bother with it rather than making arbitrary rules. Note that we now drop trailing for string entities inside of lists. They weren't needed and it makes the output look uniform whether we use a single or double newline between list elements. Conflicts: src/Haddock/Parser.hs test/Haddock/ParserSpec.hs
*	Allow for headings inside function documentation.	Mateusz Kowalczyk	2014-01-12	1	-2/+12
\| \| \| \| \| \| \| \| \| \| \| \| \|	LaTeX will treat the h3-h6 headings the same as we'd have to hack the style file heavily otherwise and it would make the headings tiny anyway. Hoogle upstream said they will put in the functionality on their end. Conflicts: src/Haddock/Interface/Rename.hs src/Haddock/Types.hs test/Haddock/ParserSpec.hs
*	Support for bold.	Mateusz Kowalczyk	2014-01-12	1	-2/+13
\| \| \| \| \| \| \|	Conflicts: src/Haddock/Backends/Hoogle.hs src/Haddock/Interface/Rename.hs src/Haddock/Parser.hs
*	Fix totality, unicode, examples, paragraph parsing	Simon Hengel	2014-01-12	1	-280/+202
\| \| \| \| \| \| \| \|	Also simplify specs and parsers while we're at it. Some parsers were made more generic. This commit is a part of GHC pre-merge squash, email fuuzetsu@fuuzetsu.co.uk if you need the full commit history.
*	Don't append newline to parseString input	Simon Hengel	2014-01-12	1	-18/+12
\| \| \| \|	We also check that we have parsed everything with endOfInput.
*	One pass parser and tests.	Mateusz Kowalczyk	2014-01-12	1	-0/+435
	We remove the HTML test as it is no longer necessary. We cover the test case in spec tests and other HTML tests but keeping this around fails: this is because the new parser has different semantics there. In fact, I suspect the original behaviour was a bug that wasn't caught/fixed but simply included as-is during the testing.