| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
The benefit of this is that the ‘top-level’ element of such lists is
properly wrapped in <p> tags so any CSS working with these will be
applied properly. It also just makes more sense.
Pointed out at jgm/pandoc#1346.
|
|
|
|
|
| |
I can not remember why they were wrapped in paragraphs to begin with and
it seems unnecessary now that I test it. Closes #307.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(so that we can use haddock-library with doctest)
|
| |
|
| |
|
|
|
|
|
|
|
| |
When using HEAD, we build haddock-library directly from repository as a
dependency (and thanks to --enable-tests, the tests get ran anyway). In
all other cases, we manually run the tests on haddock-library only and
don't test the main project.
|
| |
|
|
|
|
|
| |
I think you either add src to hs-source-dirs or the library to
build-depends. But doing both does not make sense (AFAICT).
|
| |
|
| |
|
|
|
|
|
| |
Update repository urls, use subdir property for haddock-library and use
a separate versioning scheme for haddock-library in preparation for release.
|
|
|
|
|
| |
Style-sheets are no longer a recent thing, dead links, old maintainers,
different formats.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit e110e6e70e40eed06c06676fd2e62578da01d295.
Apparently as per GHC commit ac2796e6ddbd54c5762c53e2fcf29f20ea162fd5
this was actually intended. Embarrasing for me.
|
|
|
|
|
|
| |
This reverts commit 57aa591362d7c8ba21285fccd6a958629a422091. I am
reverting this because I pushed it to master when it was meant to stay
on a wip-branch. Sorry Gergo and everyone who had trouble due to this.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
As I can not figure out how to do this properly, if we're in GHC tree,
we treat the library as being the same package. If we're not in the
tree, we require that the library be installed separately.
|
|
|
|
|
| |
We can now drop some Maybe tests and even lets us strip an error
handling monad away in a few places.
|
|
|
|
| |
They are much more useful to the users here.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We have to generalise the Doc (now DocH) slightly to remove the
dependency on GHC-supplied type.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting with GHC 7.10, System.Exit exports the new `die`
which is essentially the same as Haddock.Util.die, so this
commit changes Haddock.Util.die to be a simple re-export
of System.Exit.die. See also
https://ghc.haskell.org/trac/ghc/ticket/9016
for more details.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #298.
|
| |
|
| |
|
|
|
|
|
| |
This stops people with 7.6.3 trying to install 2.15.x which clearly
won't work. Unfortunately we shipped 2.14.x without realising this.
|
|
|
|
|
|
|
| |
The order of signature groups has been corrected upstream. Here we add a
test case and update some existing test-cases to reflect this change. We
remove grouped signature in test cases that we can (Minimal,
BugDeprecated &c) so that the test is as self-contained as possible.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes bug #294.
This also fixes a related but never-before-mentioned bug about the
display of GADT record selectors with non-polymorphic type signatures.
Note: Associated data type constructors fail to show up if nothing is
exported that they could be attached to. Exporting any of the data types
in the instance head, or the class + data family itself, causes them to
show up, but in the absence of either of these, exporting just the
associated data type with the constructor itself will result in it
being hidden.
The only scenario I can come up that would involve this kind of
situation involved OverlappingInstances, and even then it can be
mitigated by just exporting the class itself, so I'm not going to solve
it since the logic would most likely be very complicated.
|
|
|
|
| |
Fixes #201.
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
|
|
|
|
| |
Involves tiny cleanup of all the dynflag bindings. Fixes #292.
|