Maybe redo should keep cursor where modification happens (not respecting pure line change in redoing)?

[Giessen]

Steps to reproduce:

1. Change any content (say input balabala at line 10) and performe undo, the added balabala is erazed and the cursor changes to where it happens. (OK)
2. Change cursor position to any other line (say line 5). Performe redo:
   expected: balabala reappears and cursor position stays after balabala (like Nano or Vim)
   actual: balabala reapears but cursor position redirects to line 5 (actully I cannot see what is redone because cursor not staying there after redo)

Any ideas? thanks a lot!

[dmaluka]

Which version of micro?

I'm not observing this problem with the newest micro or with 2.0.13.

[Giessen]

I git clone the most recent version that is 2.0.13 and make build it. But I run micro --version, it outputs:
Version: 0.0.0-unknown
Commit hash: Unknown
Compiled on Unknown
I cannot make it work correctly, by referencing to some related issues:
#1582

The redo redirecting cursor problem still exists.

[dmaluka]

When I clone and build the newest micro:

git clone https://github.com/zyedidia/micro
cd micro
make build

the version it shows is:

% ./micro -version
Version: 2.0.14-dev.245
Commit hash: 2259fd10
Compiled on August 03, 2024

and the redo cursor problem is not observed.

Could you maybe describe the exact steps you are doing to download, build and run micro?

[Giessen]

My OS: WSL2
Shell: Zsh

This time, I do EXACTLY same as you did. When I run ./micro --version and get exactly same output as yours.

I deleted .config/micro folder totally and reopen ./micro:

1. Type 123 at line 11
2. move cursor to line 7
3. Ctrl-z to undo, then Ctrl-y to redo.
   Cursor moves to line 7 (expected being after 123 at line 11).
   Problem is still there. Very wierd...

[dmaluka]

Ah, got it: you undo after moving the cursor to another line.

Yeah, I can reproduce it this way. I've actually recalled that this issue (i.e. cursor unexpectedly jumping far away after a redo) was annoying me sometimes. Yeah, it would be good to fix it.

[Giessen]

I can confirm it's solved. Thanks.

[phil294]

Thanks so much for fixing this <3

As a long-time micro user, this was the only remaining issue for me. Such a great project!