There are a few issues we need to address regarding SciLexer before release. They are all just cosmetic issues with Ruby syntax highlighting in Ruby. The problem is with the actual library, and is not fixed. Unfortunately, this bug has been present for a while, and there is no future outlook on it being fixed, as can be seen here where one of the developers basically says he has no interest in fixing it.
Here is a little list of the syntax highlighting errors that occur:
- Keywords after the keyword "def" do not colorize, specifically "def self.method_name".
- The keywords "if", "unless", "until", and "while" do not colorize when used after the first word of a line.
- In Ruby range operators ".." and "...", the first dot inherits the color of a number, not an operator.
Now we all know that these issues are fixable, as RMXP and most other programs that use SciLexer have the issue fixed, but unfortunately I cannot fix this on the Python side. The problem is with the optimized way Scintilla searches for what it need to colorize, not any type of rule that can be defined via its Python wrapper, at least as far as I know. As you may have noticed, Gemini suffered from the same problem. I tried replacing the build of SciLexer with the each one of RMXP ,RMVX, and Notepad++ SciLexers, all to no avail. Although some bugs like the "def self.whatever" were fixed, it caused a slew of other coloring bugs, so I didn't use it.
Anyways, I'm just posting this up to make you all aware. Hopefully SOMEONE on the team who is good with C++ can check into what it would take to get this fixed.