I can’t really get the variables and non-primitive types to be highlighted (you are seeing the variables in light blue just because i made everything in light blue)
Also the fact that it does not accept anything else but .sublime-syntax in yaml and .tmTheme in xml is kinda, ehm, incompatible with things you may find online
Is there a way to make them a different color?
Well, change the styling in a .tmTheme file and use it? I don’t know if parser has a unique scope for them. If not, then you also will have to update the .sublime-syntax file. Or use text show rules for specific tokens, i.e., show "list": set text(red).
bat has a huge collection of parsers, all of which are using the .sublime-syntax. I think it’s probably the most common format in Rust ecosystem/libraries. It’s documented and all. So Typst uses it for non-Typst languages.
It’s what I’m trying to do :,(
But it doesn’t get either variables or types, it’s so strange because they are so simple things
I also tried different .sublime-syntax files but nothing
I don’t really know what to do, it’s so difficult for nothing
(Also what’s bat?)
This is bat. It’s an alternative to the ct CLI tool.
What exactly have you tried? If it doesn’t work at all, that’s a bug.
Ok i’ll provide a minimal (non)-working example
test.tmTheme:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>name</key>
<string>Visual Studio 2019 Dark (C++)</string>
<key>settings</key>
<array>
<dict>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#DADADA</string>
<key>background</key>
<string>#1E1E1E</string>
</dict>
</dict>
<!-- works -->
<dict>
<key>scope</key>
<string>storage.type</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff0000</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>punctuation</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#00ff00</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>keyword.operator</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff9900</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>constant</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#0099ff</string>
</dict>
</dict>
<!-- doesn't work -->
<dict>
<key>scope</key>
<string>variable</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff0000</string>
</dict>
</dict>
</array>
</dict>
</plist>
test.typ:
#raw("int test = 3;", lang: "c++", theme: "test.tmTheme");
result:
I tried many keys other than variable, I may not have found the right one, but I don’t know, didn’t manage to do non-primitive types as well.
But it doesn’t get either variables or types, it’s so strange because they are so simple things
These are actually hard things, due to the ridiculously complicated grammar of C++. For example can you say which or the following x are variable names?
x * y
f<x>(y)
First line: type of pointer variable, or variable in multiplication? Second line: template type of function, or variable in comparison?
Maybe for this reason, it appears that the standard sublime-syntax grammar doesn’t assign a “variable” or “entity” scope where you wish it would. So it doesn’t matter which tmTheme you use, it won’t highlight variables unless you also use an alternative syntax file. Maybe you can find one that defines the scopes you need, or create/edit it yourself…
(Hint: to find what scopes are assigned by your syntax file, in Sublime Text you can put the cursor on a word and press Ctrl+Alt+Shift+P.)
The situation might improve in the future if Typst ever supports more powerful syntax grammars like tree-sitter (see discussion on this PR: Syntax highlighting with tree-sitter 🌳 by nik-rev · Pull Request #7351 · typst/typst · GitHub)
Yeah, I guess if it’s not defined, then probably what @sijo said. You can hack around and do
#############################################################################
# The following are C-specific scopes that should not be reused. This is
# because they push into subcontexts and use variables that are C-specific.
#############################################################################
assignment:
- match: '(\w+)\s+(\w+)\s*(=)\s*(\d+)'
captures:
1: storage.type.c
2: variable
3: keyword.operator.assignment.c
4: constant.numeric.integer.decimal
global:
- include: assignment
- include: early-expressions
- match: '^\s*(?=\w+)'
push: global-modifier
- include: late-expressions
idk why, but {{basic_types}} for some reason doesn’t match… so that’s in the C file:
%YAML 1.2
---
# http://www.sublimetext.com/docs/3/syntax.html
name: C
file_extensions:
- c++
- h
first_line_match: "-[*]-( Mode:)? C -[*]-"
scope: source.c
For some reason, if I only set syntaxes to C++.sublime-syntax, the highlighting changes, but if I do C.sublime-syntax with file_extensions changed, then it seems to match. That’s strange, maybe some other version or combination is used by default.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>name</key>
<string>Visual Studio 2019 Dark (C++)</string>
<key>settings</key>
<array>
<dict>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#DADADA</string>
<key>background</key>
<string>#1E1E1E</string>
</dict>
</dict>
<!-- works -->
<dict>
<key>scope</key>
<string></string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#aaaa00</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>storage.type.c</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff0000</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>punctuation.terminator</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#00ff00</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>keyword.operator.assignment.c</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff9900</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>constant.numeric.integer.decimal</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#0099ff</string>
</dict>
</dict>
<!-- doesn't work -->
<dict>
<key>scope</key>
<string>variable</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ff00ff</string>
</dict>
</dict>
</array>
</dict>
</plist>
#raw(
"int test = 3;",
lang: "c++",
// syntaxes: ("C.sublime-syntax", "C++.sublime-syntax"),
// syntaxes: "C++.sublime-syntax",
syntaxes: "C.sublime-syntax",
theme: "test.tmTheme",
)
So, in the end nothing changes: either hack your way with custom match rules in parser, or hack your way with show rules in Typst.