cmark-gfm
cmark-gfm copied to clipboard
github
GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C
When building cmark-gfm to asm.js with Emscripten I ran into the issue that the cmark library suffers a Javascript stack overflow during loading. It happens in both debug and release...
Even if this is a commonmark fork with a bunch of work "on top of that", making sure that those change are _still_ "on top of cmark" every few years...
Here's a set of patches that I wrote as a part of packaging cmark-gfm for Debian. 1. Install more headers for library users. I'm unsure whether these are still required,...
When combining strikethrough (`~~`) with other markup, the behavior differs depending on the nesting order. - When strikethrough is nested inside, strikethrough renders correctly: - `**~~a~~**b` renders as **~~a~~**b -...
This reverts commit e08c5523b662f022a37bae28494a8c17b5c5097b from https://github.com/github/cmark-gfm/pull/289. The headers aren't duplicated on Windows and CYGWIN. There, [`CMARK_GFM_EXTENSIONS_EXPORT` resolves to `__declspec(dllexport)` and `__declspec(dllimport)`](https://gitlab.kitware.com/cmake/cmake/-/blob/4559f5770f746174927c9ec733bf5b26e2ab1efe/Modules/GenerateExportHeader.cmake#L305-307) depending on whether the dynamic library is built or...
i would love to use the `` and `` tags to denote inserted and deleted text. GFM allows them and uses the default CSS styling for them: underline for ``...
Related: #377 ```md https://ドメイン名例.jp/を参照してください。 ``` Should be "[https://ドメイン名例.jp/](https://xn--eckwd4c7cu47r2wf.jp/)を参照してください。" (`https://ドメイン名例.jp/を参照してください。`). ``` > new URL("https://ドメイン名例.jp/例?q=例").toString() 'https://xn--eckwd4c7cu47r2wf.jp/%E4%BE%8B?q=%E4%BE%8B' ``` > [!NOTE] > "ドメイン例.jp" is equivalent to "example.jp" in Japanese language. > [!WARNING] > We...
Fix for failure that's happening on macOS: https://github.com/github/cmark-gfm/actions/runs/20376412871/job/58555993240?pr=381
Potential fix for [https://github.com/github/cmark-gfm/security/code-scanning/4](https://github.com/github/cmark-gfm/security/code-scanning/4) The best fix is to explicitly add a `permissions` block specifying only the required permissions—ideally as restrictive as possible. Since this workflow is only checking out...