-
-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] support for history tree (undo redo tree) #459
Comments
So perhaps this could be made to work by editing the plugin(s) to call vscode split/window commands instead of the vim commands? Is that likely to be straighforward? |
The extension can work with a buffers originated from neovim, but will skip any initially empty ones. That's why So immediate workaround is to try to fill something when gundo/undotree buffer is being created, something like this can possibly work: autocmd BufAdd [gundo-buffer-name/wildcard] <code to insert something (any text) into the buffer> |
@asvetliakov 👍 ok that seems to sort of work:
However, yeah it takes over the whole editor, and doesn't seem to actually function to edit history because it can't find the buffer to change: Maybe the best solution would actually be a new vscode plugin that connects vim undo branches with the new VSCode Timeline view. |
That's probably because that buffer is being disconnected and inserted into new window, so original binding to parent windows is lost and breaks the plugin
I have some plans to improve such buffers support, but it would take some time. |
In plain vim, I use plugins like mbbill/undotree to see and navigate the history tree.
It would be neat to have something like this inside VS Code. So useful!
The text was updated successfully, but these errors were encountered: