Re: svn/git/etc blame compatible syntax highlighting

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: svn/git/etc blame compatible syntax highlighting

d[r]eadlock

Hi,

I re-opened this >60 days closed thread because i just discovered it
today.

Sorry to be a little bit late on this but I was just in the same
position as Richard. I already used to use vcscommand and this new
options looks terrific. The only pb i encountered was (for SVN at
least, i didn't check on other vcs') when user's name is longer than
'normal'.
Example

 1      foo  #!/bin/bash
 2      bar  # ...
 3  rogerthekingofnames #
 1      foo ls
 1      foo

After investingating a little biti think  that culprit is
   execute "normal 0zR\<c-v>G/" . splitRegex . "/e\<cr>d"

because the blockwise-visual selects only until ' 1    foo' hence,
rogerthekingofnames is cut.
I must admit i did not understand well the above command (especially
the 0zR) and did not find an 'easy' (or at least in my vim skills)
workaround.

Anyway this options is a great idea and as i'm really beginning to use
svn i think that this split-blame is a must-have even with this little
pb (and i've been a little bit surprised that googling returns so few
entries, hopefully this thread was amongst them).

Many thanks,

Marc.

PS: an other great idea could be to 'annotate' current code (i.e. just
opening a 'vsplit' for annotate stuff) and for 'locally  modified'
stuff to put special comment, but i must admit it might be a different
approach that the current vcscommands (i.e. first issue a diff to see
which lines are 'originals',  modified, removed, added to after issue
the correct 'annotate').

Bob Hiestand wrote:

> On Wed, Jan 21, 2009 at 11:26 AM, Richard Hartmann
> <[hidden email]> wrote:
> >
> > Hi all.
> >
> > if I run
> >
> >  git blame foo.file | vim -
> >
> > or
> >
> >  svn blame foo.file | vim -
> >
> > I get the blame-annotated file in Vim. Is there a way to have the syntax
> > highlighting ignore the blame stuff and simply highlight the actual
> > code?
>
> Users of the vcscommand plugin are encouraged to try a preliminary
> version that provides exactly this functionality.  It can be
> downloaded at:
>
>  http://repo.or.cz/w/vcscommand.git?a=snapshot;h=refs/heads/dev/split-blame;sf=zip
>
> Please note, the above link will give a zip with an extra directory.
> I'll package it once it has more testing and documentation.  If you
> use stock options for blame/annotate, it should Just Work as-is for
> CVS, SVN, and git.
>
> Please let me know if there are any issues with this.
>
> Thank you,
>
> bob

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---