- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi there, I'm curious if there's a way for Databricks to support syntax highlighting for a language that is currently not supported in our DBX configuration. For example, I'm using .toml files, but Databricks doesn't understand it and displays it as simple text:
In contrast, if I take my file and rename it to another file extension (such as .yaml), I get the correct syntax highlighting for that language:
Toml has been around for quite a while already, so I'm hoping this is a "solved" problem at this point, but after some initial web searching I couldn't find anything on this.
Any help on this would be greatly appreciated!
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @ChristianRRL!
Sorry for the delayed response. Databricks currently does not support syntax highlighting for .toml files. As a workaround, you can edit toml files in external editors like VS code (with plugins) and sync them to Databricks using Repos.
I’ll share your feedback with the team and see if we can support this in the future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Very small additional context, per the toml home page, this is the kind of syntaxt highlighting I would hope Databricks supports in some way/shape/form:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @ChristianRRL!
Sorry for the delayed response. Databricks currently does not support syntax highlighting for .toml files. As a workaround, you can edit toml files in external editors like VS code (with plugins) and sync them to Databricks using Repos.
I’ll share your feedback with the team and see if we can support this in the future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Ah I see. I have to admit I was hoping that I was missing something on my end, and that this would have been a simple fix somewhere in our workspace/configuration.
Thank you for listening and sharing the feedback with your team, I do hope that this is supported in the future!

