You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
The only parts not between quotes are SQLITE_UNIX_CURRENT_TS and MINUTE. However, here is the result :
I am sure that this piece of code's syntax is correct, because it compiles without errors. The problem seems to be caused by the * operator of my SQL query, ie. the following code is correctly colored :
Thanks for the report! Does this seem like a good full minimal working example of the problem? I can reproduce the issue you described with this snippet but it's always helpful to have a self-contained minimal example so just wanted to double check.
Edit by @rsese to add alternate example with 1.42.0-nightly6 on macOS 10.14.6
" - (1 * "
isn't treated as a string in this case.With Tree-sitter disabled:
Prerequisites
Description
The following string literal in C breaks syntax coloring in Atom :
"WHERE timestamp < " SQLITE_UNIX_CURRENT_TS " - (1 * " MINUTE ")";
The only parts not between quotes are
SQLITE_UNIX_CURRENT_TS
andMINUTE
. However, here is the result :I am sure that this piece of code's syntax is correct, because it compiles without errors. The problem seems to be caused by the
*
operator of my SQL query, ie. the following code is correctly colored :"WHERE timestamp < " SQLITE_UNIX_CURRENT_TS " - (1 " MINUTE ")";
As you can see :
However, removing the
-
operator breaks coloring in another way, ie. in the following code :"WHERE timestamp < " SQLITE_UNIX_CURRENT_TS " (1 * " MINUTE ")";
Which yields the following :
Steps to Reproduce
"WHERE timestamp < " SQLITE_UNIX_CURRENT_TS " - (1 * " MINUTE ")";
Expected behavior:
Coloring as in the 2nd screenshot (but including the
*
operator)Actual behavior:
Wrong coloring as in the 1st and 3rd screenshots.
Reproduces how often:
I have only seen this occurring on the exact piece of code stated in the "Steps to reproduce" section.
Versions
Additional Information
None that I can think of.
The text was updated successfully, but these errors were encountered: