RJ TextEd

I sometimes need to line up some 2-column (or N-column) text.

To do that, I create a Quick Macro that does a
SHIFT-Ctrl-Right-Arrow to select the SPACEs starting from
a column to the first word, then do a DELETE to delete those SPACEs,
and then a Down-Arrow for the next line.

So I created my Quick Macro to do that, which worked.

BUT when I press Ctrl-M to do the next lines, it not only deletes
the SPACEs, it deletes the first word of the text.

I know you changed the way that stuff works recently,
and I don't remember exactly what the resulting decisions
were after some people 'complained'.

I mentioned that if the cursor is on a SPACE (whitespace?)
then you are on a "SPACE Word", and non-SPACE characters
should be used as the delimiter.
That is always how it worked before. (?)

And that's what it does if it's not running in a Quick Macro.

Example:
When I do SHIFT-Ctrl-Right-Arrow in this forum editor, it does select
the SPACEs AND the first 'word', which I suppose is what you were
trying to do in the Editor.

I don't care for that behavior, but it's okay IF I can, in the Quick Macro,
do a SHIFT-CTRL-Left-Arrow to get to the beginning of the word text,
so I can then just DELETE the selected SPACEs.

I got around it by doing the SHIFT-Ctrl-Left-Arrow while recording the macro,
which messed up the line Real-Time, so I did an UNDO, and then just ran the macro
with Ctrl-M for each line, and it worked.

NOTE, however, that one of the e-mail addresses was ":blackhole:",
and that deleted the first COLON character. So I guess it wasn't counting
the COLON as the beginning of the word, which I also think is a BUG.

.
.

AND another weirdness.

I decided to make the table look like this:
My text has over 80 lines in the file, so this is a small example.
What I did was a bunch of REPLACEs, with SPACEs and DOTs patterns
until all of the lines were in the format of "NAME--.....--ADDRESS",
with the dashes being SPACEs and the DOTs being various lengths,
similar to this: (exaggerated here)
So I tried my Quick Macro, and it seemed to oddly delete almost
a random number of DOTs. I don't know where it thought the "Next Word" was,
but it seemed somewhat inconsistent.

I think I mentioned before when we were discussing the changes in the other post
that if the cursor is on a Non-SPACE, Non-ALPHANUMERIC character ("Punctuation"),
then you are on a "PUNCTUATION-Word", and similar rules according to what
I think SPACEs should be treated, should be used in that circumstance, too.

That just seems Consistent.

Otherwise it is kind of Chaotic Anarchy, and the command-functions become
impossible to use in a Macro, because you can't trust what they will do in
"generic circumstances" of text.

The macro actions for moving or selecting words are currently ignoring the settings you may have set in options. I've fixed it so, if you set (Shift) Ctrl+Left/Right to always move to the beginning of a word, you should get the behavior you want.

Fixed in v16.15 final.

Thanks.