Skip to content
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

Have an interface for the history tree, document it #745

Closed
lenormf opened this issue Jul 26, 2016 · 2 comments · Fixed by #2673
Closed

Have an interface for the history tree, document it #745

lenormf opened this issue Jul 26, 2016 · 2 comments · Fixed by #2673

Comments

@lenormf
Copy link
Contributor

lenormf commented Jul 26, 2016

Hi,

I edited the title of this issue to reflect the fact that it's not so much about documenting keys as it is about deciding what the interface should be and documenting how the whole undo-tree thing works.

@lenormf lenormf changed the title Document the history tree, have an interface for the history tree Document the history tree, have an interface for it Jul 26, 2016
@lenormf lenormf changed the title Document the history tree, have an interface for it Have an interface for the history tree, document it Jul 26, 2016
@lenormf
Copy link
Contributor Author

lenormf commented Jul 28, 2016

I had a look at what other editors have, and I think vim's gundo is pretty nice:

  • interactive tree visualizer: unlike emacs' implementation, the changes are a stack, not a top-to-bottom list; there's always a left-aligned straight path (representing the current branch) from which the changes branch off as opposed to a centered tree
  • diff printing: fancy syntax highlighted diffing to know what the changes do before they're applied

All this combined with tmux panes would be p gr8.

@Delapouite
Copy link
Contributor

Delapouite commented Jun 1, 2017

I have started a draft here : https://github.com/mawww/kakoune/wiki/Undo-tree to better illustrate the difference between u and <a-u>.

This document deserves a bit of editing and when it will be mature enough, it will be turned into a proper doc/manpages/undo-history.asciidoc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants