V2 - Rollback shift + tab to unindent?

[neojp]

Good afternoon,

I was wondering if is there a way to disable "Shift + Tab" to insert a regular tab, and rollback the functionality to use unindent. I'm so used to this key shortcut, that it's getting in my nerves.

Thanks!

PS. I love Sublime Text 2, look forward to the final version!

[ratnushock]

This is actually a bug related to tab_completion.
Hope John fixes it soon I also use this a lot and it's frustrating.

[iamntz]

I did it this way: Preferences->User Key Bindings-> i added this:

Code: Select all

{ "keys": ["shift+tab"], "command": "unindent" }

Work like a charm. I didn't discovered any conflicts by now.

[ratnushock]

I did it this way: Preferences->User Key Bindings-> i added this:

Code: Select all

{ "keys": ["shift+tab"], "command": "unindent" }

Work like a charm. I didn't discovered any conflicts by now.

That's already on the the Default Key Bindings file, but it needs a context which doesn't seem to work properly because of tab_completion.

Lines 140 ~ 150:

Code: Select all

...

{ "keys": ["shift+tab"], "command": "insert", "args": {"characters": "\t"} },
{ "keys": ["shift+tab"], "command": "unindent", "context":
    [
        { "key": "text", "operator": "regex_contains", "operand": "\n" }
    ]
},
{ "keys": ["shift+tab"], "command": "prev_field", "context":
    [
        { "key": "has_prev_field", "operator": "equal", "operand": true }
    ]
},

...

Anyway, I tried yours and seems to work nice, so thanks for your solution.

[bizoo]

Don't understand the problem here, or maybe it's a something related to the OS (I'm on windows).

The context { "key": "text", "operator": "regex_contains", "operand": "\n" } mean that you need a "carriage return" in the selection to trigger the unindent.
So if you want to unindent only the current line you have to press CTRL+L to select all the line and after SHIFT+TAB to unindent.
This is how ST1 work and feel right to me.

I tried some other editors (pspad, wordpad, Delphi, ...) and my conclusion is that this behavior is common to all.
If you don't select your text before un/indenting, there's no standard behavior and it depend of your editor.

[guillermooo]

I realize it's a matter of habit, but I agree with bizoo that the symmetry between Tab and Shift+Tab in selected whole lines is pretty clear.

Maybe Shift+Tab could be made to unindent if the previous character was a tab (or the beginning of the line), or do its current thing if it wasn't. A tab character as a tab trigger wouldn't make too much sense, would it?

[oats]

Shift-tab should always be unindent. Period.

I hope this changes with the next ST release.

[bizoo]

Shift-tab should always be unindent. Period.

I hope this changes with the next ST release.

Like I already said, ST1 don't work like this so it looks that this behavior was only present in the beginning of the alpha of ST2. I didn't notice it myself.
So if you want it, do it yourself http://www.sublimetext.com/forum/viewtopic.php?f=3&t=2059#p9525

[elmer]

It's great pain in the ass for me. For now I decided to downgrade to Alpha Build 2056 - last version I found without this bug (feature??).

[oats]

What ST1 did is irrelevant. The best default behavior for Shift-tab is unindent. I think that makes the most sense for most people. Key bindings are always available for those who want something different.