Am 01.11.2011 20:03, schrieb Georg Brandl:
>> TAB was bound to cycling previously and now again.
>
> But what it does now is *not* cycling as it did before. When I enter a
> line that is correctly indented, pressing TAB once should do nothing.
OK, that's a difference.
>
>> If it's just to jump to outmost reasonable indent, call
>> py-indent-line directly.
>
> BTW, "outmost indent" is ambiguous to me. I assume you mean the largest
> reasonable indentation?
yes
>
>> Or bind it to TAB to avoid cycling.
>
> But I like cycling, just not the way it's done right now. Even if this
> behavior is kept, I question its usefulness as a default behavior.
>
Will re-introduce that do-nothing-first-when-on-largest-indent
and close the bug when done.
Am 01.11.2011 20:03, schrieb Georg Brandl:
>> TAB was bound to cycling previously and now again.
>
> But what it does now is *not* cycling as it did before. When I enter a
> line that is correctly indented, pressing TAB once should do nothing.
OK, that's a difference.
>
>> If it's just to jump to outmost reasonable indent, call
>> py-indent-line directly.
>
> BTW, "outmost indent" is ambiguous to me. I assume you mean the largest
> reasonable indentation?
yes
>
>> Or bind it to TAB to avoid cycling.
>
> But I like cycling, just not the way it's done right now. Even if this
> behavior is kept, I question its usefulness as a default behavior.
>
Will re-introduce that do-nothing- first-when- on-largest- indent
and close the bug when done.