-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
[FEATURE] - Syntax highlight for case statement #74
Comments
Hi @gkong09 , Could you provide more details about it? I mean, the Thank you |
Hello Alessandro,
Thanks for the reply.
I've attached 2 screenshots to show the difference between built-in lazarus
settings and vscode.
Because of how pascal is made, the 'case of' statement is at the top, and
it's really difficult to see the actual case statements.
In other languages such as C you will have the 'case' for each case to
indicate that this is a new entry and it will be highlighted.
It becomes a bit messy when you have a lot of case statements or nested
ones.
Let me know what you think,
…On Sun, Feb 28, 2021 at 7:29 PM Alessandro Fragnani < ***@***.***> wrote:
Hi @gkong09 <https://github.com/gkong09> ,
Could you provide more details about it?
I mean, the case statement is already highlighted, as the keywords case,
of, else and end are highlighted.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#74 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMBVVZ347ITQNZURHRC6QVDTBLNXDANCNFSM4YIYDQWA>
.
|
Hi @gkong09 , No screenshots available (maybe GitHub doesn’t import screenshots when comments are made by e-mail). Whenever possible, please update the screenshots, so I could take a look. Thank you |
If I understood correctly, you would like each case item ( I’m not sure the Syntax Highlight API that VS Code provides (and the extension uses) does support this feature. I guess it would require to move to Semantic Highlight API. I’ll take a look. Hope this helps. |
Yes exactly. I understand that it may not be possible/hard to do. |
No description provided.
The text was updated successfully, but these errors were encountered: