... | ... | @@ -530,7 +530,9 @@ supporting markdown. |
|
|
|
|
|
It also lacks special mechanisms for more elaborate markups like
|
|
|
[admonitions](http://docutils.sourceforge.net/0.7/docs/ref/rst/directives.html#admonitions) (or generally: "semantic meanings") or "quick links"
|
|
|
(say: bug#1234 pointing directly to the bug tracker).
|
|
|
(say: bug#1234 pointing directly to the bug tracker). (Note that there
|
|
|
*are* special extensions to handle this in Markdown, see
|
|
|
[markdown-callouts](https://github.com/oprypin/markdown-callouts) and the [admonition extension](https://python-markdown.github.io/extensions/admonition/).
|
|
|
|
|
|
It has to be said, however, that Markdown is widely used, much more
|
|
|
than the alternatives (e.g. asciidoc or rst), for better or for
|
... | ... | @@ -740,6 +742,7 @@ possible to run CI on changes in GitLab wikis. |
|
|
[muffet](https://github.com/raviqqe/muffet), [hyperlink](https://github.com/untitaker/hyperlink), [more](https://gitlab.torproject.org/tpo/tpa/ci-templates/-/issues/14#note_2843661))
|
|
|
* [forspell](https://github.com/kkuprikov/forspell): wrapper for hunspell, can deal with (Ruby, C, C++)
|
|
|
source code, local dictionaries
|
|
|
* [ls-lint](https://ls-lint.org/): linter for filenames
|
|
|
|
|
|
See also [this LWN article](https://lwn.net/Articles/822969/).
|
|
|
|
... | ... | |