Wednesday, September 18, 2013

Re: Scrolling (diffing) through VCS revisions


On Sep 18, 2013 8:11 PM, "Paul" <google1241@rainslide.net> wrote:
>
> On Tuesday, 17 September, 2013 at 17:51:14 BST, Ben Fritz wrote:
>>
>> :VCSVimDiff BASE
>> :VCSVimDiff PREV
>> :VCSVimDiff COMMITTED
>> :VCSVimDiff HEAD
>> :VCSVimDiff {2006-02-17}
>>
>> All these are supported by Subversion running from a command-line in place of a numeric revision. Do they work from the vcscommand plugin commands? If so you don't need any plugins or any knowledge of specific revision numbers.
>
>
> They do work with VCSVimDiff, but I think they only help with diffing against the last change only.
>
> For example, foo.txt was changed in revisions 2, 3, 5, 9, 10, 11. HEAD is now at revision 20. I want to open foo.txt in Vim, then do something so that it diffs against the last change made to it. :VCSVimDiff PREV would diff the current (local) version against revision 11. That's fine, but I want to do that something again so that I then see a diff between the current local version and revision 10. Then again for 9, 5, etc., effectively seeing a nice vimdiff of the changes to foo.txt throughout its lifetime.
>
> Currently what I have to do is 'svn log' on foo.txt, note the revisions, and do a :VCSVimDiff for each one. It's that process that I'd like to know if it can be done automatically at the stroke of a keypress.

Aurum is capable of doing this: :AuVimDiff, then gJ for previous and gK for next revision with modifications, but its subversion and bazaar backends are least stable as the only place where I use both VCSes is aurum test suite. Feel free to report bugs to https://bitbucket.org/ZyX_I/aurum/issues.

Note: gJ and gK should be typed in the buffer with repository version, not in the buffer with version from current working directory. J and K are for just next/previous revision. If you are diffing two revisions they should work for both (in fact it is aurum://file mapping, not the AuVimDiff-specific one).

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> --- You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: