(Shift) + Shortcut + Left/Right skips only 1 word boundary, not 2

[JordanMartinez]

This fixes #200. I could write a test for it, but that would require adding a TestFX test dependency in headless mode so that the travis build still works correctly.

[JordanMartinez]

Any comments on this?

[TomasMikula]

I'm afraid this fix would cause the caret to move like this, i.e. sometimes skipping just the space:

|foo bar baz
foo| bar baz
foo |bar baz
foo bar| baz
foo bar |baz
foo bar baz|

[JordanMartinez]

.... isn't that kind of the point? If it's something you don't want in RTFX, then that issue should have been closed a long time ago.

[TomasMikula]

I think this is the desired behavior:

When moving to the right:

• If there is a space to the right of the caret, then skip two boundaries.
• If there is a word character to the right of the caret, then skip just one boundary.

Analogously when moving to the left.

This is different from both the current state and this PR.

[JordanMartinez]

The new commit should do it.

[JordanMartinez]

Shouldn't this also factoring in tabs?

[TomasMikula]

I would use isWhitespace.

[JordanMartinez]

How's that?

On another hand, it doesn't work if there are multiple blank lines between one word and the next. The caret | by word1 would stop twice before reaching word2:

word1|

|

|word2

Is that desired?

[TomasMikula]

Well, that is also the current behavior. I think it is a problem of BreakIterator.getWordInstance() that it considers a line break as a word boundary.