Both possibilities could be an feature.
I just wanted to think about.
I think it is fine as it is right now, but maybe for your code you should keep the door open for alternatives.
- - -
Just for reference the both possibilities form my POV:
Case A
* default: edit all but not empty lines
* if i want to modify the column in non-empty lines too, i would fill those line up with an special sign like ###, and use search&replace to empty the lines again afterwards
1.
AAAAAAAAAAAAAAAAAAAA
BBBBBBBBBBBBBBBBBBBBBBB
2.
AAAAAAAAAAAAAAAAAAAA
####################
BBBBBBBBBBBBBBBBBBBBBBB
3.
AAAAAAAAXXXAAAAAAAAA
#########XXX########
BBBBBBBBBXXXBBBBBBBBBBB
4.
AAAAAAAAXXXAAAAAAAAA
XXX
BBBBBBBBBXXXBBBBBBBBBBB
Case B
* default: edit all incl. empty lines (like it is right now)
* if i didn't want the empty lines to be modified, i have to delete the modifications afterwards
1.
AAAAAAAAAAAAAAAAAAAA
BBBBBBBBBBBBBBBBBBBBBBB
2.
AAAAAAAAXXXAAAAAAAAA
XXX
BBBBBBBBBXXXBBBBBBBBBBB
3.
AAAAAAAAXXXAAAAAAAAA
BBBBBBBBBXXXBBBBBBBBBBBIn both cases
* shorter lines in between should not be handled specifically, they are just non-empty but no data at that column. That would be anyway an special case.
- - -
Alex> "what is the default: I do not want to have..."
The default could be an setting in XML for that session.
Of course it is always better to have an case-wise setting, i.e. switchable from menu...
but i think it would be enough to have at least an session-wise setting to allow the user to set his/her preferences.
Let's talk about for version 12 or so
