Will there be a .sublime-something replacement for the .tmPreferences file format?

[frou]

It seems to me that we’re down to .tmPreferences being the last Sublime related file that must be in Apple PLIST format.

[kingkeith]

Deprecating tm* settings files (and maybe using YAML)

Editing tm* files (tmPreferences, tmLanguage, tmTheme) just sucks. This post is to convince the developer(s?) to deprecate the tm* files and possibly implement a new language settings system. I tried to structure it somehow well but considering I wrote this over 3 days it might still be a bit complex. Don't hesitate to ask if you can't follow or don't understand something. Probably the only reason why tm* files are used seems to be backwards compatibility with TextMate. However, the reasons ag…

Isn't it the time to move from tmTheme format to a YAML based color scheme definition

Following the discussion regarding the structure of Packages at sublimehq/Packages#32, there also are: *.tmMacro (not supported by ST according to @FichteFoll) *.tmCommand (not supported by ST according to @FichteFoll) *.tmDragCommand (not supported by ST according to @FichteFoll) *.tmPreferences *.tmSnippet which has *.sublime-snippet as a replacement however *.sublime-completions are treated differently by ST although they might seem similar

Syntax Fun

First of, awesome! Secondly, but muh time. At this stage, no. YAML if a great format if you're familiar with it, but the syntax can be quite unintuitive at times (e.g., exactly when a string needs to be quoted is not always obvious). I'm not ruling it out, it's just something I'm approaching with caution. This is somewhat true, sadly. Once you understand the rules behind it it becomes rather simple and when assisted by a linter (such as sublimelinter-pyyaml) you can probably catc…

Preferences json not yaml?

@math2001 Jon and I have discussed the idea of using YAML. There are some definitely pluses to it, but some downsides also. One of the bigger issues is that significant whitespace isn’t intuitive to many users unless they’ve worked with a language like Python before. Using it for .sublime-syntax was a big win over XML or JSON. The additional complexity of understanding YAML was justified there since writing a syntax definition isn’t the sort of thing most users do. We haven’t made a definitive …

[frou]

Thanks for the references Keith.

Is the following the full landscape? Anything missing or incorrect in my table?

Extension	Format	Obsoletes
.sublime-build	JSON
.sublime-color-scheme	JSON	.tmTheme
.sublime-commands	JSON
.sublime-completions	JSON
.sublime-keymap	JSON
.sublime-macro	JSON
.sublime-menu	JSON
.sublime-mousemap	JSON
.sublime-package	ZIP
.sublime-project	JSON
.sublime-settings	JSON
.sublime-snippet	XML	.tmSnippet
.sublime-syntax	YAML	.tmLanguage
.sublime-theme	JSON
.tmPreferences	PLIST

[BPL]

Nice, check below if there are something you would like to add to your table:

import sys
from pathlib import Path

print("\n".join(sorted(list({
    v.suffix for v in Path(sys.argv[1]).glob("**/*.sublime*")
} | {
    v.suffix for v in Path(sys.argv[1]).glob("**/*.tm*")
}))))

output:

.cache
.rcache
.sublime-build
.sublime-color-scheme
.sublime-commands
.sublime-completions
.sublime-keymap
.sublime-macro
.sublime-menu
.sublime-mousemap
.sublime-package
.sublime-settings
.sublime-snippet
.sublime-syntax
.sublime-theme
.sublime_session
.tmLanguage
.tmPreferences
.tmTheme

[frou]

Good idea. I tried sublime.find_resources myself.

I’ve added .sublime-package and .sublime_session that you found to the table. They’re kind of meta-level I guess.

Edit: There’s also .sublime_license. I won’t in fact include _session and _license because these underscore-containing ones are an implementation detail of the main app and aren’t related to extensibility.