[Bf-committers] Text editor: "tab as space" as default? do we really need to push PEP8 that way?

Dalai Felinto dfelinto at gmail.com
Sat Mar 6 21:16:33 CET 2010

It looks like people really like spaces (no problems with that, as I said,
no pep8 discussion here).
My main problem with converted tabs is: (1) I use the Text editor for glsl
shaders as well  (2) the need to manually go deal with every space
individually to perform operations such as deleting and navigating (going
back and forward in a line).

So how about if we not only convert tabs to space but also jump 4 spaces
when moving left, and remove 4 spaces if we delete a 'tab' ? I can take a
look at how other script editors deal with that, but suggestions would also
be welcome.


2010/3/5 Paolo Ciccone <phciccone at gmail.com>

> One more voice in favor of tabs as spaces. TextMate, the editor that I use,
> and Emacs, can handle that situation very well.
> But what's more important, tabs have been proven in several occasions to
> lead to inconsistent presentation of the code.
> They are a "relative" entity, while a given amount of spaces will always
> appear as originally intended. When code uses a
> mix of tabs and spaces, and that happens often when inserting hard tabs,
> the
> resulting indentation goes often haywire.
> When I hit Tab I expect the editor to indent and align my code in a
> consistent manner, based on the language used.
> In Emacs pressing tab in the middle of the line, not just at the beginning,
> performs that operation. So, there is clearly
> a separation between what the key does and its ASCII representation.
> ---
> Paolo Ciccone
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list