-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
New tokens format & theme matching #17933
Conversation
- remove ILineTokens.actualStopOffset - remove stopAtOffset - refactor MonarchLexer
# Conflicts: # src/vs/editor/contrib/suggest/common/snippetCompletion.ts # src/vs/editor/node/textMate/TMSyntax.ts
@alexandrudima So all tokens are now hidden behind This merge has caused an issue displaying key-value pairs with different colors, but without being able to see the new tokens I have no way to address it in tmThemes or custom grammars. |
@joshpeng You can use https://marketplace.visualstudio.com/items?itemName=siegebell.scope-info to see a hover with the scope hierarchy at the given position. |
@aeschli Thanks for the extension link, but this extension seems to only show the original VSC scopes. It doesn't seem to be capable of showing scopes from custom grammar extensions. |
Before we could piggy back off of VS Code's |
@aeschli @joshpeng Please use This will show you the token you are on and three sections:
|
@joshpeng scope-info should work for custom grammar extensions, but if conflicting grammars are provided by multiple extensions or vscode, then I bet it is picking the wrong one. With |
Fixes #11597
Fixes #16206
Fixes #3008
TODO:
ViewLineToken
model.getMode()
andmodel.getModeId()
LanguageIdentifier.sid
andLanguageIdentifier.iid
token
class name from every tokenstandaloneColorService
check editor with bootstrap css(created follow up task)vscode-textmate
vscode-textmate
vscode-textmate
dom
layer breaker fromTMSyntax.ts