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

Template strings and keyword colorization #1716

Closed
DickvdBrink opened this issue Jan 18, 2015 · 6 comments
Closed

Template strings and keyword colorization #1716

DickvdBrink opened this issue Jan 18, 2015 · 6 comments
Labels
Duplicate An existing issue was already created Fixed A PR has been merged for this issue

Comments

@DickvdBrink
Copy link
Contributor

See screenshot, only happens after the ${num} stuff
Running VS 2013

Because I didn't have an ending */ the whole file is now shown as a comment

capture
@DanielRosenwasser DanielRosenwasser added the Duplicate An existing issue was already created label Jan 18, 2015
@DanielRosenwasser
Copy link
Member

Known issue and duplicate of #1477 and #1698. Unfortunately this won't work in VS2013 but it does for VS2015.

@DanielRosenwasser
Copy link
Member

@DickvdBrink if you're still interested, there's a partial fix here: #1698 (comment)

@DanielRosenwasser DanielRosenwasser mentioned this issue Feb 2, 2015
Closed
@DanielRosenwasser
Copy link
Member

A fix is now in master.

@DanielRosenwasser DanielRosenwasser added the Fixed A PR has been merged for this issue label Feb 13, 2015
@DickvdBrink
Copy link
Contributor Author

Wow, I didn't saw this until today xD Thanks @DanielRosenwasser

@DanielRosenwasser
Copy link
Member

You're very welcome! Did you just see the change with 1.5-alpha?

@DickvdBrink
Copy link
Contributor Author

Yes, I made a build myself and the above one was fixed! Thanks!

@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Duplicate An existing issue was already created Fixed A PR has been merged for this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DickvdBrink @DanielRosenwasser