Fix python call syntax highlighting#1987
Conversation
9c941a1 to
42fd161
Compare
|
@tancnle I've rebased this (had some conflicts) but it seems to have broken match/case. Would you mind taking a look? |
|
@jneen I have rebased and resolved the conflicts. Could you please have another look?
|
|
@jneen Good catch. I think the included example does not demonstrate the changes introduced by this branch correctly (item
|
|
Hey Tan, Can you explain in your own words the meaning of this table and how you constructed it? To which changes are you referring? Which revisions are you referring to with "new" and "old"? The code on main is significantly newer than the code in this repository. |
|
@jneen I ran each of test example with ❮ echo "self.list" | ./bin/rougify -l python -f null
Name "self"
Punctuation "."
Name "list"
Text "\n"
Apology I could be more specific. I will need to submit another patch to point out the problematic parts. |


Summary
Fixes an issue with the Python lexer where any identifier used before an opening paren
(would be highlighted as a function name. This led to inconsistent highlighting in the case offorloops, where oneforwould be rendered as a keyword while the other was rendered as a function name:This pull request also addresses other edge cases for call expressions:
Visual Before and After