<feed xmlns='http://www.w3.org/2005/Atom'>
<title>haddock.git/test, branch ghc-gitlab-ghc-head</title>
<subtitle>Haddock with an org backend (haddorg).
</subtitle>
<id>https://g.ypei.me/haddock.git/atom?h=ghc-gitlab-ghc-head</id>
<link rel='self' href='https://g.ypei.me/haddock.git/atom?h=ghc-gitlab-ghc-head'/>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/'/>
<updated>2014-05-05T09:00:41+00:00</updated>
<entry>
<title>Move parser + parser tests out to own package.</title>
<updated>2014-05-05T09:00:41+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-05-05T07:01:03+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=cc269e6b0b615e9e237c35a985e4ace7b9ab0dd9'/>
<id>urn:sha1:cc269e6b0b615e9e237c35a985e4ace7b9ab0dd9</id>
<content type='text'>
We move some types out that are necessary as well and then
re-export and specialise them in the core Haddock.

Reason for moving out spec tests is that if we're working on the parser,
we can simply work on that and we can ignore the rest of Haddock. The
downside is that it's a little inconvenient if at the end of the day we
want to see that everything passes.
</content>
</entry>
<entry>
<title>Prepare modules for parser split.</title>
<updated>2014-05-05T07:19:49+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-05-05T03:16:19+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=7ac2d0f2d31c2e1c7ede09828f3d5ba5626bd0d4'/>
<id>urn:sha1:7ac2d0f2d31c2e1c7ede09828f3d5ba5626bd0d4</id>
<content type='text'>
We have to generalise the Doc (now DocH) slightly to remove the
dependency on GHC-supplied type.
</content>
</entry>
<entry>
<title>Initialise some new PlatformConstants fields</title>
<updated>2014-04-03T20:19:24+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-04-03T20:19:24+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=b1420ef9c8fdb2728128ad51fb0b636f69932eb7'/>
<id>urn:sha1:b1420ef9c8fdb2728128ad51fb0b636f69932eb7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Drop leading whitespace in @-style blocks.</title>
<updated>2014-03-31T17:29:04+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-03-31T17:29:04+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=d6cf6f9c75e08ce1760c2dbdee81775ba97a5f0c'/>
<id>urn:sha1:d6cf6f9c75e08ce1760c2dbdee81775ba97a5f0c</id>
<content type='text'>
Fixes #201.
</content>
</entry>
<entry>
<title>Add default for new PlatformConstraints field</title>
<updated>2014-03-31T15:53:25+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-03-31T15:53:25+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=8c64228d1b5d63714697a3df1a89e0d6dfc9b095'/>
<id>urn:sha1:8c64228d1b5d63714697a3df1a89e0d6dfc9b095</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Turn a source code comment into specs</title>
<updated>2014-02-22T20:55:35+00:00</updated>
<author>
<name>Simon Hengel</name>
<email>sol@typeful.net</email>
</author>
<published>2014-02-22T20:55:35+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=dfc006ad2b8f5cb27570ac02c77aa63c5c027cd9'/>
<id>urn:sha1:dfc006ad2b8f5cb27570ac02c77aa63c5c027cd9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Strip a single leading space from bird tracks (#201)</title>
<updated>2014-02-22T20:31:03+00:00</updated>
<author>
<name>Niklas Haas</name>
<email>git@nand.wakku.to</email>
</author>
<published>2014-02-22T20:15:34+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=fc7fd1875d31dbfd37eaa058177e534b4fc6bc25'/>
<id>urn:sha1:fc7fd1875d31dbfd37eaa058177e534b4fc6bc25</id>
<content type='text'>
This makes bird tracks in the form

&gt; foo
&gt; bar
&gt; bat

parse as if they had been written as

&gt;foo
&gt;bar
&gt;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.
</content>
</entry>
<entry>
<title>Fix @ code blocks</title>
<updated>2014-01-30T16:22:34+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2014-01-29T20:37:10+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=7d2106e18f26a680d157ef943da2602e7199afa1'/>
<id>urn:sha1:7d2106e18f26a680d157ef943da2602e7199afa1</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Allow escaping in URLs and pictures.</title>
<updated>2014-01-12T20:48:36+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2013-09-16T02:01:29+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=deb106d8250b7582e01f78e88c88ca7465fc0bc1'/>
<id>urn:sha1:deb106d8250b7582e01f78e88c88ca7465fc0bc1</id>
<content type='text'>
Some tests were moved under parseString as they weren't about paragraph
level markup.

Conflicts:
	src/Haddock/Parser.hs
	test/Haddock/ParserSpec.hs
</content>
</entry>
<entry>
<title>Allow for nesting of paragraphs under lists.</title>
<updated>2014-01-12T20:48:36+00:00</updated>
<author>
<name>Mateusz Kowalczyk</name>
<email>fuuzetsu@fuuzetsu.co.uk</email>
</author>
<published>2013-09-08T00:28:57+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/haddock.git/commit/?id=a03c93524ba2ca4143c10770a2fa0dd134b57a83'/>
<id>urn:sha1:a03c93524ba2ca4143c10770a2fa0dd134b57a83</id>
<content type='text'>
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
</content>
</entry>
</feed>
