Haddock with an org backend (haddorg). https://g.ypei.me/haddock.git/atom?h=ghc-9.4 2022-07-21T02:27:19+00:00 2022-07-21T02:27:19+00:00 Yuchen Pei hi@ypei.me 2022-07-21T02:27:19+00:00 urn:sha1:32ac0f03b4259fc8eebba9bb3a2a46d23122a43b 2022-05-08T14:19:47+00:00 Artem Pelenitsyn a.pelenitsyn@gmail.com 2022-05-08T14:19:47+00:00 urn:sha1:4073ed3534eea6579869679bdb59ea3322c2a588 2022-05-03T12:19:24+00:00 Ben Simms ben@bensimms.moe 2022-05-03T12:19:24+00:00 urn:sha1:35c99f595c984f58d2fb4dc180c48a0eaf7df173 * Keep track of ordered list indexes and render them * Rename some identifiers to clarify 2022-05-03T11:34:04+00:00 Phil de Joux philderbeast@gmail.com 2022-05-03T11:34:04+00:00 urn:sha1:bc0f2d6c1bfd331a9426fa9a92288444178267b1 2022-04-12T11:29:46+00:00 Steve Hart steve.hart@americandata.consulting 2022-04-12T11:29:46+00:00 urn:sha1:e06c1c255377e5245748f4c4003240815deae72f * Catch Markdown links at beginning of line within paragraph Per Issue #774, Markdown links were being parsed as ordinary text when they occurred at the beginning of a line other than the first line of the paragraph. This occurred because the parser was not interpreting a left square bracket as a special character that could delimit special markup. A space character was considered a special character, so, if a space occurred at the beginning of the new line, then the parser would interpret the space by itself and then continue parsing, thereby catching the Markdown link. '\n' was not treated as a special character, so the parser did not catch a Markdown link that may have followed. Note that this will allow for Markdown links that are not surrounded by spaces. For example, the following text includes a Markdown link that will be parsed: Hello, world[label](url) This is consistent with how the parser handles other types of markup. * Remove obsolete documentation hint Commit 6b9aeafddf20efc65d3725c16e3fc43a20aac343 should eliminate the need for the workaround suggested in the documentation. 2022-04-06T15:47:57+00:00 askeblad 74082607+askeblad@users.noreply.github.com 2022-04-06T15:47:57+00:00 urn:sha1:a127bb256ec411b2e78edba21299c5dabba3b847 2022-03-16T08:44:27+00:00 askeblad 74082607+askeblad@users.noreply.github.com 2022-03-16T08:44:27+00:00 urn:sha1:e187816f64f0c54dc924f8283fe4c75a6e1f67b2 2022-03-14T19:32:30+00:00 Vladislav Zavialov vlad.z.4096@gmail.com 2020-10-18T13:25:35+00:00 urn:sha1:b02188ab1cc46dd82395a22b04f890cf15f3feae 2021-02-07T16:46:25+00:00 alexbiehl alexbiehl@gmail.com 2021-02-07T16:46:25+00:00 urn:sha1:2f34d120c6da996d23518c3fa9065ccf0e05a551 Instead construct the ModLink value directly when parsing. 2021-02-07T15:13:04+00:00 Iñaki García Etxebarria git@inaki.blueleaf.cc 2019-07-31T15:28:00+00:00 urn:sha1:c31c156422785751e33c9a7a4f021ac8da77d364 Support a markdown-style way of annotating module references. For instance -- | [label]("Module.Name#anchor") will create a link that points to the same place as the module reference "Module.Name#anchor" but the text displayed on the link will be "label".