CSS perfect completion should work mainly in 3 stages:

1.Selector: HTML element (tag) completion (not realized in Sublime Text 2);

2.property name completion (realized in Sublime Text 2);

3.property value completion (realized in Sublime Text 2).

Completion must start with HTML element (tag) completion (format with curly brackets {}) (not realized in Sublime Text 2). Completion should include Universal, Class, Id, Descendant, Child, Adjacent sibling, Attribut, Pseudo-class and Pseudo-element Selector (not realized in Sublime Text 2).

HTML element (tag) completion must be followed by property name completion (not all the properties, but only the specific property, for a specific HTML element).

Property name completion must be followed by property value completion (not all the values, but only the specific values for a specific property).

knowing what keys it have will greatly support developing context aware plugins

So, I have this neat idea when it comes to navigation a file solely by the keyboard.

Here's how it works (Consider a class, as in programming):

You are at line 8, adding a class property. Then, you quickly move your cursor down to line 25, type your method and realize you need to rename the property. Now, since you've "been" at line 25 for a few seconds, sublime "remembers" that position, now when you quickly move back up to line 8 and rename your property, you can hit hotkey X to return to the previous "remembered" line.

What do you think?

The "time" required to stay at a line for it to be "remembered" could be like 3-5 seconds or perhaps user configurable.

It would be awesome if plugins could dynamically modify the autocomplete list. That would allow for context specific autocomplete. Even something like an event asking plugins if they have any suggestions to add to the autocomplete list (before it pops up, or async while it's displayed) would be a nice start.

I have a 2000 line long file whose sidebar minimap exceeds the height of the sidebar window.  With the cursor located at the top of the file, the sidebar view actually represents around lines 1-250 in the file.  If I click at the mid-point of the sidebar view then ST2 should go to line 125 (1/2 way down the visible map), but in fact it goes to line 1000 (1/2 way down the actual file).  I'd expect it to go to the section of text that I clicked on in the minimap.

Have you tried different price points? (I'm sure you have, but i'm curious as to why).  $70 seems an awful lot for an (albeit amazing) text editor.  I'd buy this with a smile on my face for $30, but $70 is simply too much.

I would like to be able to set a property such as `"default": true` when defining build systems within project files. Once this is set, then pressing ctrl-b within a project would automatically execute the default build process (unless you explicitly select something else).

Perhaps instead of a boolean, it could be a list of extensions or regexes: `"default": ["*.py"]`, so that the specified build system becomes the default for, in this case, only Python files. And you could specify something else for e.g. CoffeeScript files.

My particular use case is this: I have a project template with which I distribute a sublime-project.json file. Projects using this template are always going to use a virtualenv'd python at env/bin/python. So I specify this python instance in the project file's build systems. If there were a default flag, then I wouldn't have to remember to select this build system in the drop-down menu for each new project; it would just work.

This is just kind of a nicety.

I'd like that Sublime Text had all the functionalities (even better ones) of the Emmet plugin (ex Zen Code) built-in.

There are often times when I get confused as to which directory a file is in because of the way Sublime indents the files in a directory. It seems to me that the indentation should start from the beginning of the collapse/expand arrow, and not the start of the directory names. Furthermore, the expand/collapse triangle icons could be smaller to help with this.

Would like to see more complete lua syntax support without having to take Lua Dev to override default files in the Sublime install.

I've tried to set Lua Dev as default syntax for lua files, but it creates lua.sublime-settings file rather than lua dev.sublime-settings but even if I manually create it, it won't work.  It always defaults to core Lua syntax, so it should be updated if we can't replace it.

Where can I find a complete reference for keybindings and settings? 

I've already found a lot of forum comments with "insert this into your settings file" that helped in some of my problems, but right now when I tried to find the proper "context" value for the caret being in one of the groups in split view, I found nothing. (Currently I'd like to be able to move a file around in a 2x2 view with alt+ctrl+left/right/up/down and to be able to do that, I need to define different rules for every group.) And by nothing I mean not even an unexplained list with all the usable contextes. ST2 is advertised as being completely customizable which I found really promising, but without a complete reference those possibilities not already in the default files, are kind of unusable... It's okay if ST2 isn't able to do something (like my example above) but making me roam the internetz for hours trying to find some maybe not even existing (I may never know) information just doesn't seem like a good situation...