[Pharo-project] Dedicated to days of wasted time in your life, formatting source code for replacing spaces with tabs

Igor Stasenko siguctua at gmail.com
Mon Mar 12 16:50:40 EDT 2012

On 12 March 2012 21:23, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
> Igor
> would it be not more clever to integrate keyMapper and add Ctrl-a Ctrl-e
> because has that since decades now?
It is orthogonal. Ctrl-a btw selects all text.. which kind-of
windowish behavior, but it is also quite useful.

> I would not integrate such change in its current state
> Because for me going back one character is important and it is important to jump at the beginning of the line

Stef, you can go back & forth by one character, unless you are at
multiple whitespace characters,
which is treated as single whitespace.

This is not my invention. I borrowing that from typography systems, a
white space between words treated as a single whitespace,
because usually, a typography system using kerning rules and adjusts
spaces width in order to justify text in a line so it will align to
column edges.
You can take any newspaper and see the effect. Obviously, nobody using
multiple spaces in text to align it..  because space width may vary.
And hence, no need to put more than one space between words.
Tabs having special meaning , however. Usually they used at the
beginning of line.
And usually again, you don't need to be able to navigate to each
particular tab character, you always want to navigate either to start
of line, or to start of a text.. and this is 1 key stroke with my
with one finger. no need to use ctrl-a /ctrl-e

> but that I know how to do it: ctrl-A and at the end Ctrl-e.
> Cut a line Ctrl-K….
> So ...
so try format the attached. and you will see a difference

> Stef
> On Mar 12, 2012, at 3:58 AM, Igor Stasenko wrote:
>> On 12 March 2012 03:50, Igor Stasenko <siguctua at gmail.com> wrote:
>>> sorry for not explaining the feature properly..
>>> I just wanna ask, what do you think, it we're going to integrate that:
>>>  a) should it be optional or we can use it by default?
>>>  b) if it is optional, what is default setting on/off?
>>> I vote for (a).. Because:
>> ^^^
>> a) as not-optional :)
>>> What i finding hard is imagining situation, where old behavior will be
>>> less time consuming/more appropriate.
>>> Can anyone can come up with cons arguments?
>>> While is important to fully control each whitespace character(s)
>>> separately, when you editing/typing text (as in languages like Python
>>> they even make it part of syntax... (what a stupid idea.. can't resist
>>> sorry)), for navigating the text an importance of stepping over every
>>> whitespace character seems to be leaning to zero.. (well, at least in
>>> my eyes).
>>> --
>>> Best regards,
>>> Igor Stasenko.
>> --
>> Best regards,
>> Igor Stasenko.

Best regards,
Igor Stasenko.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ContextPart-doPrimitivemethodreceiverargs.st
Type: application/octet-stream
Size: 4082 bytes
Desc: not available
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120312/67429ae7/attachment.st>

More information about the Pharo-dev mailing list