can't moveDown/Up from wrapped line in visual-mode.

[t9md]

moveDown(j) , moveUp(k) can' go across wrapped line in visual-mode if selection is linewise.
No problem in selection is characterwise.

Here is example, L176 is wrapped, and cursor is L175 in visual-mode.
When I did j, I can't go down from L176. And also can't go up with k to go across wrapped line.

[t9md]

I'm now investigating, moveSelectionLinewise have some bug..

[t9md]

Issue is cursor movement(cursor. is screenPosition wise but moveSelectionLinewise is bufferPosition wise.
So even if screen position was changed by @moveCursor() of MoveUp or MoveDown motion,
this line won't care screenRow change.

I quickly implemented fix on @moveSelectionLinewise method(counting screenRows and adjust count argument passed to @moveCursor() argument, but supporting count argument is not easy since current screenRow count while moving.

So the solution I'll try next is to make moveCursor() aware of screenRowCount in linewise motion.

[t9md]

I sent PR for fix this, but this PR need discussion.

First of all other motions are currently not aware of diff of screenRow and bufferRow, so having same issue when line is softwrapped. e.g. MoveToFirstCharacterOfLineAndDown.

Theoretically all motion which do linewise motion and using simple cursor.moveDown() or cursor.moveUp() have same isssue.

Passing screenRowCount to cursor.moveUp(screenRowCount), cursor.moveDown(screenRowCount) fix this un-awareness.
By this fix, also fix dj, dk of soft-wrapped line(maybe other jk depending motion).

But this fix have side effect.
This fix making normal j, k motion bufferLineWise.
Currently j, k is screenLineWise which is atom's default and equivalent to Vim's gj and gk.

How should we handle this screenRow and bufferRow diff.

[GabeIsman]

Ran into this issue. I can move down past a wrapped line, but never up.

[lee-dohm]

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!