by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ming, Bai
    @mbbill
    good.
    Matthias Günther
    @wikimatze
    Nice to have gitter support for your plugin
    Uri Gorelik
    @uri
    You probably get asked this all the time, but you make undotree because you were unhappy with https://github.com/sjl/gundo.vim ?
    Ming, Bai
    @mbbill
    because gundo need python, and sometimes it drives me crazy.. 2.x, 3.x, x86, x64,...
    And I believe the task (managing the undo history and drawing the graph) could be done in pure vimscript without any performance penalty.
    Uri Gorelik
    @uri
    @mbbill thanks for the reply!
    Matthias Günther
    @wikimatze
    yeah, great to get away with the python dependencies of gundo
    Adam Wright
    @shaladdle
    Hello. I'm wondering if you've considered creating a new plugin (or extending undotree) which uses your tree visualization code, but shows git history instead of vim undo tree history. It seems like an obvious thing to want, and after a quick search or two I didn't see a plugin that obviously does that.
    Also your plugin is super awesome :)! Thanks for making it.
    Ming, Bai
    @mbbill
    @shaladdle glad to know people like it :smile: There are one limitation in the tree visualization algorithm if it's used for git -- it does not handle branch merge, which happens in git a lot but never happen in vim undo history. The algorithm has to be reworked quite a bit in order to support git. Except that, I think "git log --graph" or "gitk" would be enough in most situations.
    Adam Wright
    @shaladdle

    I didn't realize that you had replied until now.. Sorry - I'm new to gitter.

    There are one limitation in the tree visualization algorithm if it's used for git -- it does not handle branch merge, which happens in git a lot but never happen in vim undo history.

    Ah, that makes sense. Too bad.

    Except that, I think "git log --graph" or "gitk" would be enough in most situations.

    I assume here that you mean that running these commands should be a good alternative to having an undotree-like plugin. I disagree though, I think the ability to scroll through file history from within vim, using j/k/enter to show revisions in the current buffer is much more powerful than copying/pasting git refs all over the place.

    Talha Mansoor
    @talha131
    Is it possible to auto update the diff as I scroll down the history graph?