In order to stick with default OSbehavior and also improve the usability of creating new files I suggest assigning:

Super+N -> Open new window (like it does on textmate, finder, etc..)

Super+T -> Go to file/New file (Create new tab showing the current panel with a couple of teaks)

To open a file, it would work as usually:

Create new tab, type the name of the file, press return.

To create a file:

Create new tab and press esc to dismiss the overlay. 
As an enhanced behavior, the user could instead of pressing esc, type the name of the newfile+folder (somefolder/example.css) and press enter. If no folder is specified (example.css), the file would be created next to the previously displayed file. This would spare the user of having to save the file manually in order to have syntax features or having to deal with the save file dialog. 

All this could be complemented by a Create New File entry on the show_files overlay (the one which appears when you press super+t)

Hello I am experiencing a problem with most recent version of sublime 2. My build system (nmake) used to work just fine with previous version, but now it sometimes works and sometimes does not. When it does not work, it opens an empty dockedbuild window at the bottom, but does not show any build steps ~ text, errors etc. I know build is going on, just text is not shown. Also, when text is not shown and I click in a window with my mouse, sublime crashes. When build is going and text is shown and I click, everything is fine.

Thanks.

In Sublime Text 1, there was an option find.useSelectedText that you could set to false to prevent selected text from automatically being copied into the find box. Could this option be added into ST2?

Same usefull feature as in this sublimetext 1 plug-in : HighlightCurrentWord

In Build 2128, on OS X, going in to Full Screen or Distraction Free mode and then exiting it causes Sublime Text 2 to crash.

If you open a buffer in multiple tabs (using, for example, Goto Anything), make some changes, and save the buffer, the "file dirty" marker asterisk disappears only on the tab that was active when you saved. The other tab retains the asterisk.

Build 2032 on Mac OS X.

* Choose vertical two pane layout.
* Open a file in group 1.
* Switch to group 2. Open the same file there using Goto Anything. The same buffer now appears in two tabs, one in each group.
* Make some changes to the buffer. A "file dirty" marker asterisk appears in both tabs.
* Save the buffer. The asterisk disappears in the tab that was active when the save command was issued, but it remains in the other tab.

access to all shortcuts via api. This can be used to create suggestions for shortcuts as we type. or can be used to create plugin

Although you can e.g. ci" or ci( just fine, ci< does not work.