[Github-comments] [geany/geany-plugins] markdown: in html, generated TOC, the links are dead (#771)

Matthew Brush notifications at xxxxx
Mon Sep 10 03:38:16 UTC 2018


> I don't know precisely how Textadept's author did the conversion .md->.html

It looks like a [custom lua script](https://foicica.com/hg/textadept/file/b048357bd1be/doc/markdowndoc.lua) which uses Discount. Maybe it generates the TOC in there?

>  I still think it would be useful (as even the example pages of specifications above illustrate) to have some kind of automatic support for making a TOC. What do you think?

I agree TOC support would be useful, but if it's not part of the standard, and not part of the Markdown rendering library, then it's not going to be in the plugin. There's a pull request #747 to switch to using libcmark, so if you can get this feature added there, it will just work in the future.

> I have no idea where to get a "non-standard extension from some other Markdown renderer ". Why do you ask?

I mean you're requesting a feature (TOC auto-generation) that is not part of any Markdown standard, but rather an extension provided by whatever other Markdown tool you got it from. It's quite common to get enhancement requests to add non-standard Markdown features where the poster assumes the feature is standard but it's just some custom extension (ex. Github markdown, StackOverflow markdown, etc). This plugin doesn't implement Markdown renderer/compiler by itself, it uses separate libraries to do it, so it's not really feasible to add any special extensions directly in this plugin.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/771#issuecomment-419778373
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20180909/742b9bf9/attachment.html>


More information about the Github-comments mailing list