I create some bigger Confluence pages using their ASCII Wiki Markup / Markdown syntax [1] in geany, and then I can copy and paste the entire page into Confluence. This has the advantage of me not having to fiddle with the Confluence web page GUI for each and every detail while editing.
How can I get geany to render the wiki syntax nicer, and even let me navigate the syntax better? The syntax allows wiki document headers to be defined and it would be great if geany allowed me to navigate these headers more easily (like it does with showing a list of functions, etc).
Thanks in advance!
[1] https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html
Or can somebody kindly point me towards links or some kind of tutorial explaining how to add syntax highlighting and navigation for a new syntax / file extension for Geany? Thanks in advance!
Geany does not have direct support for Confluence but you could try a [custom filetype](https://www.geany.org/manual/current/index.html#custom-filetypes) and see how much traction you get with existing lexers and parsers.
To create a new built-in type you need a highlighting lexer and/or a tags parser, without one of those a built-in filetype won't get much more capability than a custom filetype.
Highlighting lexers are written in C++ and are taken from the [Lexilla](https://github.com/ScintillaOrg/lexilla) project and tags parsers are written in C from the [Universal CTAGS](https://github.com/universal-ctags/ctags) project. Neither of those has support for Confluence markup AFAICT.
If you get a lexer/parser accepted by those projects you can add a built-in filetype to Geany (see HACKING and the merge for the most recent language additions as examples, Julia I think).
https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html
What I see there looks a lot like [Textile](https://textile-lang.com). It was popular during the Ruby on Rails fad, and declined in tandem.
@simonhf, you may want to watch [this issue](https://github.com/zufuliu/notepad2/issues/374), just in case a downstream Textile lexer appears some day. Porting it over to match the Confluence spec should be simple enough.
github-comments@lists.geany.org