Kevin Matthes

@fox0430 Okay, I will restrict the keywords to Bash and Sh, then. Shall I add the Bash configuration files to the file extensions triggers for the syntax highlighting, if appropriate?

@fox0430 As a first enhancement I would like to suggest to also apply the new comment logic introduced in #1533 -- as soon as it is merged. In the long...

@fox0430 The YAML highlighting outputs token types for which there is no colouring scheme, yet. Thus, the default colour will be applied. Configuring further colours for those token types should...

@fox0430 I would like to add highlighting for the number types which are not coloured, yet. Is it okay if I would just map the decimal numbers' colour onto them,...

@fox0430 A further suggestion: how about relating the logo to the meaning of the editor's name? A web translator translated the Japanese origin of the name of the editor (https://github.com/fox0430/moe/blob/develop/README.md?plain=1#L151)...

@fox0430 Tree-Sitters usually have C, C++, and / or JavaScript bindings, at least those I saw so far. They are plain parsers without any syntax highlighting. The highlighting itself is...

@fox0430 We should first of all focus on finding a Tree-Sitter for Nim. When switching to Tree-Sitters, we should rather keep the highlighting support for the language Moe is written...

@fox0430 There is a Nim package for LSP: https://github.com/PMunch/nimlsp

@fox0430 @tobimensch My idea would be use other colours for the respective line numbers, inspired by how VS Code / VSCodium and related editors handle this feature. There, new lines...

@fox0430 VS Code itself only supports this feature if the edited file is tracked by Git. For inspiration, I would like to suggest the editor Kate, KDE's default GUI text...