Some dependencies in Rust "Cargo.toml" file are randomly displayed in silver color #1359
-
|
Hello, 
[dependencies]
# GUI & Windowing
eframe = { version = "0.31" }
egui_extras = { version = "0.31", features = ["serde", "all_loaders"] }
# For WASM
# wasm-bindgen = "0.2"
# wasm-bindgen-futures = "0.4"
# web-sys = "0.3"
# Icons
egui-phosphor = "0.9"
image = { version = "0.25", features = ["jpeg", "png"] }
# For scraping
chrono = { version = "0.4", features = ["serde"] }
reqwest = { version = "0.12", features = ["blocking"] } # Requête HTTP
serde = "1.0"
serde_json = "1.0" # Sérialiser / désérialiser
scraper = "0.23"
# Plot graph
egui_plot = "0.32"
# Log
log = "0.4"
simple-logging = "2.0" # Logging to file#FIXME utilité wasm ?
# Generate pdf
typst = "0.13"
typst-pdf = "0.13"
ttf-parser = "0.25"
time = "0.3" |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hello @ThibaultEbroussard, VS Code by default doesn't support Even Better TOML extension with semantic highlight off:
Even Better TOML extension with semantic highlight on:
TOML Language Support extension with semantic highlight off:
TOML Language Support extension with semantic highlight on:
Vira Theme can only assign colors to syntax scopes, but where the scopes (and colors) are applied is handled by language extensions or vscode built-in languages. Guessing you're using Even Better TOML extension, the issue is how they assign the scopes. The "random" things that becomes "white" is because they are — wrongly — considered as variables instead of property name: Wrong scopes: 
⬆ Here you can see that both
|
Beta Was this translation helpful? Give feedback.
-
|
Hello, thank you for your reply. Since I didn’t experience this issue with your Material Theme, I initially thought the problem was coming from Vira Theme. It turns out the issue is actually caused by “Even Better TOML,” so I’ll see if I can report it to them. I apologize for the confusion, and thank you again for your help. |
Beta Was this translation helpful? Give feedback.
-
|
TO be more clear, the issue is now visible due to the semantic highlight feature, which Material Theme has never supported effectively. Vira Theme now supports semantic highlight, and some semantic tokens now have proper colors. However, the issue lies in how semantic tokens are applied in the TOML language by Even Better TOML. You can also quickly fix this by disabling semantic highlight in TOML files by adding this to your settings: "[toml]": {
"editor.semanticHighlighting.enabled": false
}This will "mimic" the old Material Theme colors in all toml files. We could also fix this on our side by styling "tomlArrayKey" and "tomlTableKey" custom semantic tokens, but this would violate our standard to avoid language-specific customizations. The extension developers should use one of the standard semantic tokens available that are themeable across languages. |
Beta Was this translation helpful? Give feedback.
Hello @ThibaultEbroussard, VS Code by default doesn't support
.tomlfiles. You need an appropriate extension to get the proper highlight for toml files. Said that, how colors are applied highly depends on the extension used and how they apply syntax scopes. Here an example of how different extensions change the color syntax for toml files:Even Better TOML extension with semantic highlight off:
Even Better TOML extension with semantic highlight on:
TOML Language Support extension with semantic highlight off:
TOML Language Support extension with semantic highlight on:
Vira Theme can only assign colors to syntax scopes, but where the scopes (and colors) are applied is handled by languag…