Can't move up while linewise visual mode

[yo7]

On wrapped lines, I can't move up by hitting k while linewise visual mode (shift-v).

In the GIF below, I'm trying to move up on line 12 and keeping pressing k !! ..but I can't.

[t9md]

Softwrap not work well in vim-mode.
Workaround is to disable it.

This is the limitation long existing from long ago.
I even wrote PR to official vim-mode but stopped.
It isnt easy to fix with minor change.

atom/vim-mode#785

[yo7]

I didn't know vim-mode dosen't work well with soft wrap.

But in my case, it seems that the problem happens only with moving up. I can move down normally from wrapped lines.

[t9md]

Yes, I already described issue on vim-mode.
I cant fix this issue very soon like I described above issue and related PR on official vim-mode.
This fix involve overall cursor movement handling change.

[t9md]

Note, If you disable Line wrap and it fixed, then its same issue.
If you still can't move up even after you disable soft wrap, this is the bug I need to solve immediately.
Which is the result?

[yo7]

I think it's the same issue. I can move up if I disable soft wrap.

[t9md]

Ok thanks.
I didn't care this issue in vim-mode rerwiting process.
Now Im in the mood to start tuckling to solve this issue.
Thanks for reporting this and your GIF report is very explanatory I like it!

[yo7]

Thanks. I'm looking forward to the progress!

[t9md]

Currently cursor.moveDown(), and cursor.moveUp() move in relative position of screenPosition.
But when move 1 row up in screenPosition-wise, it still remain same bufferRow.
Movement in visual-mode is actually handled by the Motion::select and Motion::select only care its change of bufferRow.
So the movement not change bufferRow is equivalent to no-movement.

The issue user notice is or not is depending on selection.isReversed() state and the motion direction.
I think this issue only happen in visual, lineiwse interactive operation.
There is more consistent elegant way to solve this issue. but I don' want to affect other area of code in this time.
So fix should be OK at this time.

[t9md]

After some evaluation and re-thinking, then I decide to release, I will close this issue, until then keep open.

[t9md]

Released. v0.1.5.