Fanning the flames...
Posted Oct 30, 2006 20:29 UTC (Mon) by mikov
In reply to: Fanning the flames...
Parent article: GNU emacs 22 goes into pretest
I am sorry, but picture-mode is completely unusable for editing source
code. Have you tried it ? :-) I don't want to edit ASCII art, I want to be
able to move my cursor in a logical fashion.
Look at these two lines:
On line1 I can position my cursor at column 20. On line2 I can't. Why ??
Because line1 has lots of spaces added. Since I can't see the spaces, why
should I be restricted from positioning my cursor anywhere I want ? I
should be able to press down arrow from column 20 on line1 and start
typing on column 20 on line2. The editor can insert the necessary spaces
automatically - it isn't rocket science :-)
This is not theoretical. Imagine this scenario:
long long long long long long long BUG1 more text.
longer longer longer longer longer BUG2 more text.
After fixing BUG1 I intuitively press the down arrow to move towards BUG2
and fix it too. Surprise - the cursor disappears and moves far to the left
by 'foo' at column 4. Why ?? What dark magic is restricting the cursor
from some areas of the screen ??
No matter, I press the down arrow again. At this time different editors
choose to do different things:
- Some keep the cursor cursor at column 4, so I have to move it all the
way to BUG2 again. Total and utter cr*p.
- Others try to be smart and move the cursor to BUG2 because they remember
the old position. Of course that is completely illogical - why should
moving the cursor DOWN from column 4 on line 2 result in positioning it at
column 20 on line 3 ??
The only logical behavior is to allow free movement of the cursor in all
directions and automatically insert spaces when necessary. Many editors
under DOS used to do that - it is actually the simplest to implement.
to post comments)