Yuchen Pei writes:
> I do wonder what is the best way to handle cross-package links.
> Currently I'm using CUSTOM_ID in the format of
> package-name-x.y.z.Module.Name.IdentifierName, as well as
> Module.Name.IdentifierName. But this is a "one big org file" approach,
> and can make navigation
On Tue 2022-07-19 21:58:26 +0800, Ihor Radchenko wrote:
> Yuchen Pei writes:
>
>> Given this is not the official version of haddock and my changes are in
>> haddock-api, I'm calling it haddorg-api, for lack of a better name /
>> approach. I'll be happy to contribute my changes upstream if a
>>
Yuchen Pei writes:
> Given this is not the official version of haddock and my changes are in
> haddock-api, I'm calling it haddorg-api, for lack of a better name /
> approach. I'll be happy to contribute my changes upstream if a
> different license covering my contribution (AGPLv3+) is
Hello,
I decided to write an Org backend to Haddock[1], so that haskell library
documentation can be generated in org mode markup. Compared to the
existing backends (html, latex and hoogle), the org format allows
utilising features like the infinite levels of heading hierarchy,
flexible folding
