Keywords taken from official manual: https://nim-lang.org/docs/manual.html#lexical-analysis-identifiers-amp-keywo... Identifiers list expanded with:
1. Some basic types from the [System module](https://nim-lang.org/docs/system.html) which is always implicitly imported.
2. Additional keywords (`lent, spawn, parallel`) from Nim [experimental features](https://nim-lang.org/docs/manual_experimental.html#view-types).
Styling and build-menu settings taken from @HJarausch config in #2669
Fixes #2669 You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2988
-- Commit Summary --
* <a href="https://github.com/geany/geany/pull/2988/commits/ede3f1a983733800a4c11ced3274dc687ffcce01">Update Nim filetype config</a>
-- File Changes --
M data/filedefs/filetypes.Nim.conf (58)
-- Patch Links --
https://github.com/geany/geany/pull/2988.patch https://github.com/geany/geany/pull/2988.diff
Can a nim user test and comment?
@ZoomRmc pushed 1 commit.
d0bdcc507ea757c5b9a0f0eff468800ceafae776 Fixup: Nim filetype: add `sink`
Nim user here, new keywords/types seem to highlight correctly :+1:
@ZoomRmc pushed 1 commit.
ddbd3ac704776869231532f1be43473b9faa4ca9 Add multiline comments to Nim filetype
Current settings use Python lexer for Nim files, however Lexilla already has a [lexer for Nim](https://github.com/ScintillaOrg/lexilla/blob/master/lexers/LexNim.cxx). This requires an additional PR, but I don't know the process of incorporating scintilla/lexilla updates Geany uses, so, please, advice.
With Python lexer multiline comments (and, perhaps, something else) don't work.
Probably best to wait for the new Scintilla to be merged to Geany before adding Lexilla parsers.
@elextr what need to be done to move forward with this?
I guess since another Nimist has commented this can be merged.
As for adding Lexers or parsers, that needs somebody who is interested to make a PR.
Merged #2988 into master.
github-comments@lists.geany.org