Sublime Text 2 understands syntax in a manner that should make nested syntax highlighting possible.

Within a certain syntax scope, e.g. string.quoted.double.java, support the creation of rules by the user which will cause a syntax-mode switch for the contents of that text's scope.

For example, we might create a rule: when in string.quoted.double.java, if the contained text matches /^SELECT/, apply .SQL syntax highlighting to that text instead.

A set of reasonable default rules could be assembled, e.g. for detecting stringified HTML and SQL in many languages, for Javascript within HTML <script> tags, etc. Allow toggling of these rules with a new View menu item "Nested syntax highlighting".

This could also be used to support per-file syntax highlighting in the find-in-all-files result buffer.

Some additional rule/configuration may be required to handle comprehension of string concatenation which varies by language, e.g. "some" + "thing" and multiline concatenations. Sublime would need to apply a nexted syntax-mode to all the parts of such a string whenever the (whole) string matches a rule.

The rules' criteria should support arbitrary python for cases which don't match a regex well; that code should be able to examine the parent scopes' text to make its assessment (e.g. examining a string variable's declared name in one's code to determine the string's syntax).

In a given file the user should be able to arbitrarily change the syntax-mode of any individual syntax-scope in any buffer, through the right click context menu or other method.

Make the default result list in Goto File/Anything (before you have typed anything) ordered by when you last opened the file, so that the previous file you worked on is at the top, the file you opened before that second etc. This would make keyboard based file navigation much more efficient, imho.

Currently, one can only expand or collapse a folder by clicking on the arrow to the left of its name. This presents a very small click target. Being able to double-click anywhere on the folder name would be a massive usability improvement for navigating these trees.

If the user has a global keyboard shortcut defined that conflicts with a Sublime Text default binding, then Sublime Text will capture the keyboard shortcut. Currently, you need to edit the global key bindings file to disable these default shortcuts.

Allow the user to "unbind" a default key binding in the user key bindings file.