aboutsummaryrefslogtreecommitdiff
path: root/haddock-library
Commit message (Collapse)AuthorAgeFilesLines
...
* Read files for hyperlinker eagerlyalexbiehl2017-04-111-1/+1
| | | | This also exposes Documentation.Haddock.Utf8
* Merge branch 'ghc-head'Ben Gamari2017-03-101-1/+1
|\
| * Bump base upper boundBen Gamari2016-12-131-1/+1
| |
* | Version bumps (2.17.3, 1.4.2)Sebastian Meric de Bellefon2016-06-031-1/+1
| |
* | Make parser state a newtypeDavid Feuer2016-05-241-1/+1
|/ | | | | | Previously, it was `data` wrapping a `Maybe`, which seems a bit silly. Obviously, this can be changed back if anyone wants to add more fields some day.
* Bump versionsBen Gamari2016-05-101-1/+1
|
* Version bumps and changelogBen Gamari2016-01-061-1/+1
|
* Fix the documentation for haddock itself.Dominic Steinitz2015-12-213-9/+20
| | | | | | | | | | | | | | | Change notation and add support for inline math. Allow newlines in display math. Add a command line option for the mathjax url (you might want to use a locally installed version). Rebase tests because of extra url and version change. Respond to (some of the) comments. Fix warnings in InterfaceFile.hs
* Handle inline math with mathjax.Dominic Steinitz2015-12-212-1/+16
|
* Canonicalise Monad instancesHerbert Valerio Riedel2015-12-141-3/+3
|
* Relax upper bound on `base` to allow base-4.9Herbert Valerio Riedel2015-12-141-1/+1
|
* Delete trailing whitespaceMateusz Kowalczyk2015-07-071-2/+2
|
* Add arbitrary-indent spec test for parser.Łukasz Hanuszczak2015-06-031-0/+17
|
* Make nested lists count indentation according to first item.Łukasz Hanuszczak2015-05-271-35/+46
|
* Create simple method for indentation parsing.Łukasz Hanuszczak2015-05-271-0/+9
|
* haddock-library: require GHC >= 7.4Adam Bergmark2015-05-111-1/+1
| | | | | | | | `Data.Monoid.<>` was added in base-4.5/GHC-7.4 Closes #394 Signed-off-by: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
* Post-release version bumps and changelogMateusz Kowalczyk2015-03-281-1/+1
|
* Update test to account for \r filteringMateusz Kowalczyk2015-03-261-2/+5
|
* Filter '\r' from comments due to Windows problems.Vincent Berthoux2015-01-221-2/+3
| | | | | On Windows this was causing newline to be rendered twice in code blocks. Closes #359, fixes #356.
* Only keep one Version instead of blindly appendingMateusz Kowalczyk2014-12-172-10/+17
|
* Various fixups and bumps for next releaseMateusz Kowalczyk2014-12-121-1/+1
|
* Disambiguate string-literalsHerbert Valerio Riedel2014-12-121-4/+4
| | | | | | | | GHC fails type-inference with `OverloadedStrings` + `Data.Foldable.elem` otherwise. Conflicts: haddock-library/src/Documentation/Haddock/Parser.hs
* Bump ‘base’ constraintMateusz Kowalczyk2014-12-121-1/+1
| | | | Follows the similar commit made on ghc-head branch
* Import Data.Word w/o import-listHerbert Valerio Riedel2014-12-121-1/+1
| | | | | | | This is needed to keep the compilation warning free (and thus pass GHC's ./validate) regardless of whether Word is re-exported from Prelude or not See https://ghc.haskell.org/trac/ghc/ticket/9531 for more details
* Update doctest parts of commentsMateusz Kowalczyk2014-12-101-18/+22
|
* Allow the parser to spit out meta-infoMateusz Kowalczyk2014-12-104-10/+59
| | | | | | | | | | | | | | | Currently we only use it only for ‘since’ annotations but with these patches it should be fairly simple to add new attributes if we wish to. Closes #26. It seems to work fine but due to 7.10 rush I don't have the chance to do more exhaustive testing right now. The way the meta is output (emphasis at the end of the whole comment) is fairly arbitrary and subject to bikeshedding. Note that this makes test for Bug310 fail due to interface version bump: it can't find the docs for base with this interface version so it fails. There is not much we can do to help this because it tests for ’built-in’ identifier, not something we can provide ourselves.
* List new module in cabal fileMateusz Kowalczyk2014-12-091-0/+1
|
* (wip) Add support for @since (closes #26)Simon Hengel2014-11-166-23/+82
|
* State intention rather than implementation details in Haddock commentSimon Hengel2014-11-161-1/+1
|
* newtype-wrap parser monadSimon Hengel2014-11-084-3/+131
|
* Minor code simplificationSimon Hengel2014-11-081-4/+3
|
* Fix parsing of identifiers written in infix wayMateusz Kowalczyk2014-11-042-11/+18
|
* Allow an optional colon after the closing bracket of definition listsSimon Hengel2014-11-032-16/+28
| | | | | This is to disambiguate them from markdown links and will be require with a future release.
* Add support for markdown imagesSimon Hengel2014-11-032-15/+21
|
* Allow markdown links at the beginning of a paragraphSimon Hengel2014-11-032-5/+43
|
* Add support for markdown links (closes #336)Simon Hengel2014-11-033-10/+69
|
* parser: Try to parse definition lists right before text paragraphsSimon Hengel2014-11-031-1/+1
|
* Minor refactoringSimon Hengel2014-11-031-22/+28
|
* Remove unused language extensionsSimon Hengel2014-11-032-5/+0
|
* Derive more instancesSimon Hengel2014-11-031-8/+1
|
* Get rid of StandaloneDerivingSimon Hengel2014-11-031-10/+3
|
* Remove -fobject-code from .ghciSimon Hengel2014-11-021-1/+1
| | | | (this slows down reloads on modifications)
* Bump haddock-library versionMateusz Kowalczyk2014-08-311-1/+1
|
* Fix warningSimon Hengel2014-08-201-0/+1
|
* Fix #313 by doing some list munging.Mateusz Kowalczyk2014-08-153-21/+37
| | | | | | I get rid of the Monoid instance because we weren't satisfying the laws. Convenience of having <> didn't outweigh the shock-factor of having it behave badly.
* Fix forgotten srcMateusz Kowalczyk2014-08-081-1/+1
|
* Update to attoparsec-0.12.1.1Mateusz Kowalczyk2014-08-0817-728/+979
| | | | There seems to be memory and speed improvement.
* Catch mid-line URLs. Fixes #314.Mateusz Kowalczyk2014-07-282-2/+6
|
* Bump haddock-library to 1.1.0 for releaseMateusz Kowalczyk2014-06-251-1/+1
|
* Don't mangle append order for nested lists.Mateusz Kowalczyk2014-06-252-22/+10
| | | | | | | | 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.