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#] wrong colorization for unsafe code pointer #1093

Closed
jonnyguo1988 opened this issue Dec 8, 2015 · 3 comments
Closed

[c#] wrong colorization for unsafe code pointer #1093

jonnyguo1988 opened this issue Dec 8, 2015 · 3 comments
Assignees
@aeschli
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Backlog

Comments

@jonnyguo1988
Copy link

pointer

hi
please see the attachment, I'm writing unsafe code in c#, but the color for the parameters of pointers is wired, I think this should be a bug.

Thank you
@egamma egamma added bug Issue identified by VS Code Team member as probable bug languages-basic Basic language support issues labels Dec 8, 2015
@aeschli aeschli changed the title code format for unsafe code Pointer [c#] code format for unsafe code Pointer Dec 8, 2015
@aeschli
Copy link
Contributor

aeschli commented Dec 8, 2015

Same problem with Atom (languages-csharp 0.11.0)
image

@aeschli aeschli changed the title [c#] code format for unsafe code Pointer [c#] wrong colorization for unsafe code pointer Dec 8, 2015
@aeschli aeschli mentioned this issue Dec 8, 2015
Closed
@aeschli
Copy link
Contributor

aeschli commented Dec 8, 2015

This issue was moved to atom/language-csharp#46

@aeschli aeschli closed this as completed Dec 8, 2015
@aeschli aeschli reopened this Dec 8, 2015
@aeschli aeschli added upstream Issue identified as 'upstream' component related (exists outside of VS Code) c# and removed languages-basic Basic language support issues labels Dec 8, 2015
@egamma egamma modified the milestone: Backlog Dec 10, 2015
@aeschli aeschli removed the bug Issue identified by VS Code Team member as probable bug label Mar 17, 2016
@aeschli
Copy link
Contributor

aeschli commented Mar 17, 2016

Now tracked in dotnet/vscode-csharp#101

@aeschli aeschli closed this as completed Mar 17, 2016
@ivanz ivanz mentioned this issue Aug 18, 2016
Merged
@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
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
@egamma @aeschli @jonnyguo1988