Undo (Ctrl+Z) does not undo correctly (wrong placement of cursor)

[mixer]

Steps to reproduce

1. Select a word in the middle of a sentence.

2. Press Ctrl+B (to make it bold)

3. Press Ctrl+Z to undo.

4. BUG: the selection is no longer around the original word you selected, but is 2 positions/characters further down. You can continue steps 2+3 further.

5. Press Home.

6. Press Ctrl+B (to make it bold). 4 asterisks will appear with the cursor positioned after those four characters, instead of inside them. Btw. this is another bug that received no response so far: Pressing Home and ctrl+b/ctrl+i shortcut causes text to be inserted after asterix

7. Press Ctrl+Z to undo.

8. BUG: the selection is no longer at the beginning of the line, but is 4 positions/characters around the original word you selected, but is 2 positions further down. You can continue steps 2+3 further.

Environment

• Operating system: Linux Mint 20.2 Cinnamon
• Obsidian version: 0.12.10

Additional info:

Somewhat related topic:

Select with Shift+home and Shift+end

Steps to reproduce So, enter text multiple lines length without linebreaks; Put cursor at middle of any of these lines. Shift+home and Shift+end Expected result Both should have same result with different half of line or whole text: “Home” should select from line start to cursor and “End” same with end of line OR “Home” select from start of this text and “End” to end of this text Actual result Mixed behavior. Home select to begin of line and End select to end of text Environment Win10x6…

[WhiteNoise]

It had a response. It was marked as reproduced.

[mixer]

You mean the “repro” tag?

From the forum newbie’s point of view:

1. It’s small and hard to notice. It’s not as visible as for example a separate “I confirmed the bug and the developers were informed. Thank you!” message from moderators.
2. It’s hard to know what it means and who added it.
3. It is even harder to understand that that’s where the moderators would make any changes; that the bug reporter should look among the tags he filled in to see any new changes that should represent the change in bug report’s status. This is very non-trivial logic.

[WhiteNoise]

Thanks for the suggestion.

[WhiteNoise]

will be fixed in 0.12.13