New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support rasi config character type options #1131
Support rasi config character type options #1131
Conversation
Handle the `xrm_Char` case in the (rasi theme) config file parser. This should properly handle configuration like ``` matching-negate-char: "\0"; ``` and ``` matching-negate-char: "-"; ```
`mem` shouldn't ever be set when `XrmOption` is `type` `xrm_Char`. Therefore, there is no need to check it and free it. Remove that logic.
...and missing period.
Add a `CHAR` token that takes things of the form `'<char>'` or some specific backslash escape sequences like `'\''` and `'\0'`. For now, save it as a `T_STRING`.
Instead of using strings for property elements of type char, use characters, which were recently added to the grammar.
Codecov Report
@@ Coverage Diff @@
## next #1131 +/- ##
==========================================
- Coverage 33.97% 33.96% -0.02%
==========================================
Files 40 40
Lines 11522 11531 +9
==========================================
+ Hits 3915 3916 +1
- Misses 7607 7615 +8
Continue to review full report at Codecov.
|
thanks. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When trying to set
matching-negate-character
in a rasi config file,the following warning shows
This is because character types are not yet handled. Handle them from
the lexer all the way to xrm options. The format shall be single quotes
containing a single ASCII character (except newline) or certain escaped
character sequences, namely
\'
\0
\\