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

textmate/yaml.tmbundle has problems with yaml literal style #13601

Closed
tnikodym opened this issue Oct 12, 2016 · 2 comments
Closed

textmate/yaml.tmbundle has problems with yaml literal style #13601

tnikodym opened this issue Oct 12, 2016 · 2 comments
Assignees
@aeschli
Labels
*out-of-scope Posted issue is not in scope of VS Code

Comments

@tnikodym
Copy link

  • VSCode Version: 1.6.0
  • OS Version: OS X El Capitan (10.11.6)

See the screenshot below. When a colon is used inside literal content (indicated by | character), the entire line up to the colon is highlighted as a property.

screen shot 2016-10-12 at 16 27 17

Note: I have not seen this issue in the previous version of VSCode.
@aeschli
Copy link
Contributor

aeschli commented Oct 14, 2016

This issue was moved to textmate/yaml.tmbundle#17

@aeschli aeschli closed this as completed Oct 14, 2016
@aeschli aeschli mentioned this issue Oct 14, 2016
Open
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
@aeschli aeschli changed the title Incorrect highlighting when colon is used inside yaml literal style textmate/yaml.tmbundle has problems with yaml literal style Sep 4, 2018
@aeschli
Copy link
Contributor

aeschli commented Sep 4, 2018

Looks like a limitation of TextMate.
Moving away from TextMate for yaml would be major investment and currently not planned.

@aeschli aeschli added the *out-of-scope Posted issue is not in scope of VS Code label Sep 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aeschli aeschli

Labels
*out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aeschli @tnikodym