On 11/26/2017 12:44 AM, Lex Trotman wrote:
On 26 November 2017 at 05:07, H agents@meddatainc.com wrote:
Are there any plans to broaden support for markdown syntax to include e.g. commonmark markdown? I have a particular interest in support for tables myself but expanded markdown support would be great.
I depends what you mean by "support", if you mean highlighting of markup that needs to be provided by Scintilla (www.scintilla.org) first so ask/provide a patch there first.
If there is some change that to the structure that the parser needs to support you can provide a patch/pull request on Geany (since the markdown parser isn't part of Universal Ctags). There are no known plans to change the existing parser, pull requests are welcome.
If you want the markdown plugin to support it, you will need to provide a patch/pull request to the markdown parser used by the plugin. There is a parser included in the plugin but IIUC the plugin defaults to libmarkdown if its available and I expect most distros use that, so you would need to get changes in that project. Alternatively you could change the embedded parser and force use of that when you built the plugin for yourself.
Cheers Lex
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Thank you for your exhaustive reply. I just checked out scintilla and the maintainer/developer calls it a lexer, not a parser. My understanding from reading this is that scintilla does the lexical analysis and then a parser does the actual interpretation.
I am looking for the markdown previewer in geany to correctly interpret table information, or perhaps the entire commonmark definition. The geany markdown plugin does not do that whereas e.g. the gedit markdown preview does do it.
So, is this both lexer and a parser issues? My - limited - understanding is both. Because the table definition information in a markdown document is not highlighted, thus presumably not recognized by the lexer, nor, of course, properly parsed in the preview, i.e. a parser issue.
Is this correct?