ST2 offers autocomplete results frequently, and in this context a TAB keystroke means "accept default autocomplete" to many users.

I asked wbond about this (in context of his excellent SFTP plugin browser), and he replied,

"I agree with you that it would make sense if the Sublime quick panel would accept using the tab key to select an item. Unfortunately there isn't any way with the Sublime API to do that. I tried adding a key binding with a context so that it would only affect the quick panel, however I could not get it to fake the enter key when I press tab."

I would be a very happy user if ST2 was to either -

1. Treat TAB as ENTER (=accept selected result) in autocomplete contexts, or

2. Permit plugin authors to override the default behaviour of accepting TAB as text entry.

There might be valid reasons for typing a TAB character in a panel, but I think that would be far less common a use case than using it for autocomplete.

re-open last closed tab : ctrl+shift+t (> 1 level of close)

move tab right-left : ctrl+shift+pageUp/Down

   keyboard entry: ctrl+arrows

   multiple-mouse-clicks: cmd+click

   mouse-drag: alt+drag

Clearly this is confusing (to say the least). I don't know about others, but (as an old textmate user) I would go with alt in all cases.

In addition I found no way to extend a rectangular selection by using the shift. Namely, I would like to click somewhere in the file, move around as I like without moving the cursor and then with a combo (say alt+shift+click) 'rectangular'-select the portion of text between the cursor and the current click. 

Also, is there any way sublime can remember that word press is suppose to be enabled? As in every document I open with have it enabled by default.