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

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Drop DocParagraph from front of headers	Mateusz Kowalczyk	2014-06-25	2	-6/+10
\| \| \| \| \|	I can not remember why they were wrapped in paragraphs to begin with and it seems unnecessary now that I test it. Closes #307.
*	Fix anchors. Closes #308.	Mateusz Kowalczyk	2014-06-25	2	-3/+21
\|
*	Update Travis, bump version	Mateusz Kowalczyk	2014-06-19	1	-1/+1
\|
*	Fixed haddock warnings.	John MacFarlane	2014-06-18	1	-6/+4
\|
*	Removed reliance on LambdaCase (which breaks build with ghc 7.4).	John MacFarlane	2014-06-18	1	-3/+3
\|
*	Remove doctest dependency	Simon Hengel	2014-06-18	2	-19/+0
\| \| \| \|	(so that we can use haddock-library with doctest)
*	Use doctest to check examples in documentation	Simon Hengel	2014-06-18	3	-0/+22
\|
*	Comment improvements + few words in cabal file	Mateusz Kowalczyk	2014-06-18	2	-11/+32
\|
*	haddock-library: Use -Wall for specs	Simon Hengel	2014-06-18	1	-0/+2
\|
*	haddock-library: Do not depend on haddock-library in test suite	Simon Hengel	2014-06-18	1	-2/+0
\| \| \| \| \|	I think you either add src to hs-source-dirs or the library to build-depends. But doing both does not make sense (AFAICT).
*	Compatibility with older versions of base and bytestring	Simon Hengel	2014-06-18	4	-3/+21
\|
*	Update cabal files	Mateusz Kowalczyk	2014-06-18	1	-2/+3
\| \| \| \| \|	Update repository urls, use subdir property for haddock-library and use a separate versioning scheme for haddock-library in preparation for release.
*	Update issue tracker URL for haddock-library	Mateusz Kowalczyk	2014-05-14	1	-1/+1
\|
*	Move out Show and Eq instances to Types	Mateusz Kowalczyk	2014-05-05	2	-8/+8
\| \| \| \|	They are much more useful to the users here.
*	Move parser + parser tests out to own package.	Mateusz Kowalczyk	2014-05-05	22	-0/+3686
	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.