View undo/redo history visually or an indicator or a counter

Dear VSCode,

Thank you very much for this project.

Although, the feature we might need is the Undo/Redo history like in the VS2019 or Photoshop, for example:

Visual Studio 2019	Photoshop

or at least colored/highlighted buttons(without any history list) or counters (these numbers below show the number of Undoings the coder did (or number of Redo available to restore)):

or an indicator if any Redo is available.

The reason of this request is that without it the VSCode forces you to recheck if any edits have undone after returning to the project by clicking Ctrl+Shift+Z/Ctrl+Y and Ctrl+Z repeatedly etc. to ensure and not lose the undo/redo history by an accident.

In short, the there are 3 ways to implement.

1. The Undo/Redo history window(like on 1 picture above)
2. A global or per file Redo available counter(like on 2 picture above)
3. A global or per file Redo indication (Redo exists or not)

Just, imagine a situation:

You are coding a big code.
1. Ctrl+Z in one file so to view some code you rewrote.
2. Open/View different file.
3. Forget that you Undo first one
4. Return to first one
5. Write 1 char or reformat/beatify it accidentally
6. The whole Redo history of first file is **GONE** ... oops (what if full block of such or even more?!)

So, this request might eliminate this problem.

It might be already nearly implemented: The Undo/Redo might already is stored in some object map or such, so just iterate through and do stuff. I.e. show the map in list or length of each map per file.

Interesting link which shows how might Emacs have such “feature”.

Best regards

[vscode-triage-bot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[JacksonKearl]

Bot counts +1 reactions on the original issue. Added a section to the docs and a link to it to the comment. See: https://github.com/microsoft/vscode/issues/102982