Shift+UpArrow VS Shift+DownArrow, when leaving selection

[RaffaeleBianc0]

Description

micro on Windows Terminal here.
Minor issue, so tiny that I am filing it as a feature request rather than a bug - i hope i'm doing this right.

Shift+UpArrow selects text, then you press anyArrow key and the cursor is in the upper part of the selection as expected (same experience you have in any windowed text editor).

INSTEAD:
Shift+DownArrow selects text, then you press anyArrow key and the cursor is in the upper part of the selection instead of the lower part: this is quite annoying, forcing you to jump down N lines again.

[JoeKar]

Which micro version did you use and can you give a bit more detailed reproduction case?

[dmaluka]

Shift+UpArrow selects text, then you press anyArrow key and the cursor is in the upper part of the selection as expected (same experience you have in any windowed text editor).

INSTEAD: Shift+DownArrow selects text, then you press anyArrow key and the cursor is in the upper part of the selection instead of the lower part: this is quite annoying, forcing you to jump down N lines again.

You probably have a typo somewhere?

Anyway, since #3091 + #3268 micro's behavior is consistently the following: if there is a selection, then:

• if you press Up or Left key, the cursor is at the upper part
• if you press Down or Right key, the cursor is at the lower part

regardless of how you created this selection - via Shift+Up or via Shift+Down (i.e. regardless of the "direction" of selection).

If that is the behavior you want, you just need to use a newer version of micro.

If, however, you want micro to take the direction of selection into account, - that was also discussed in #3091. I was actually suggesting that it would be probably more intuitive to take the direction into account, and that indeed that seems to be the behavior implemented by most editors. However, other participants wanted specifically the current direction-agnostic behavior. I was basically fine with either option, so we ended up with the current behavior.

And BTW now thinking about it again, perhaps in micro's case the current direction-agnostic behavior is actually more intuitive, since micro doesn't display the cursor when there is a selection, so the user doesn't see where the cursor is within the selection, and the user does not necessarily remember the "history" of the selection either (IOW from the user perspective it looks like there is no cursor at all, there is just the selection).