Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[C++] invalid token on closing bracket #3840

Closed
pgrit opened this issue Mar 8, 2016 · 4 comments
Closed

[C++] invalid token on closing bracket #3840

pgrit opened this issue Mar 8, 2016 · 4 comments
Assignees
@aeschli
Labels
bug Issue identified by VS Code Team member as probable bug languages-basic Basic language support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Backlog

Comments

@pgrit
Copy link

pgrit commented Mar 8, 2016

The syntax highlighting for C++ is broken in Version 0.10.10. The results differ depending on the color scheme.

Tested on Windows 10 and CentOS 7

Dark+:
broken_syntax_highlighting_dark

Dark:
broken_syntax_highlighting_dark
@MariusWiik
Copy link

Can confirm the same issue with python and C also. Seemed to get fixed when changing to Dark+. Tested in Mac OS X El-Capitan

@aeschli aeschli added languages-basic Basic language support issues bug Issue identified by VS Code Team member as probable bug labels Mar 11, 2016
@aeschli aeschli changed the title [C++] syntax highlighting broken in 0.10.10 [C++] invalid token on closing bracket Mar 11, 2016
@aeschli aeschli mentioned this issue Mar 11, 2016
Open
@aeschli
Copy link
Contributor

aeschli commented Mar 11, 2016

This issue was moved to textmate/c.tmbundle#39

@aeschli aeschli closed this as completed Mar 11, 2016
@aeschli
Copy link
Contributor

aeschli commented Mar 11, 2016

Python and C would be different issues and not related.

This issue has to do with the C++ grammar. It's not a regression.

@aeschli aeschli reopened this Mar 11, 2016
@aeschli aeschli added this to the Backlog milestone Mar 11, 2016
@aeschli aeschli added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Mar 11, 2016
@aeschli
Copy link
Contributor

aeschli commented Feb 21, 2017

Looks better now in 1.10 insiders.
image

@aeschli aeschli closed this as completed Feb 21, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aeschli aeschli

Labels
bug Issue identified by VS Code Team member as probable bug languages-basic Basic language support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@aeschli @MariusWiik @pgrit