Highlighting config conflicts with default Sublime Text highlight settings
See original GitHub issueBoth the default syntax highlighting and the highlighting included in this package are named Rust
, leading to a naming conflict where the built-in highlights take priority. Because they are named the same, any attempts to rebind back to the highlights included in this package fail. This could probably be fixed by renaming these highlights to “Rust Enhanced”, removing the naming conflict.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
[QT22] EASILY fix syntax highlighting issues in Sublime Text 4
Sublime Text 4 contains not only new features, but also performance enhancements as well. One of those relates to syntax highlighting, ...
Read more >Build 3114 - syntax highlighting - Sublime Forum
Just go to the Sublime Text menu and select Preferences then “Customize Color Scheme”. This reveals an editor showing the default settings for ......
Read more >How to Enable Syntax Highlighting in Sublime Text 3
Sublime Text 3 is a very flexible text editor with a lot of helpful ... to configure a section of code to use...
Read more >How to disable Highlighting on sublime text 3? - Stack Overflow
If you use Preferences > Package Settings > Anaconda > Default , you can see all of the settings that Anaconda supports, and...
Read more >Customization - LSP for Sublime Text
Many of the default key bindings (visible in the left view) are disabled to avoid conflicts with default or user key bindings. To...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just ran into this problem.
Add the following into your
Preferences.sublime-settings
file:I found how to do this via: http://www.tomhartwig.nl/blog/sublime-text-2-remove-syntaxes/
ok thanks @dashed i’m closing this issue.