[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon, 24 Oct 2005 18:45:33 -0500
bill pursell wrote:
> The exact command that I'm using is:
> command! -nargs=? RcsDiff vnew | set bt=nofile | exe 'r !co <args> -p
> #' | 0d_3 | diffthis | wincmd p | diffthis
> Basically, it uses the "co" command with a -p to put the desired file
> on the standard output. The difficulty with using cvs to do something
> similar is that I have to figure out which components of the path to
> the current directory are contained in the path relative to $CVSROOT.
> I'm sure I could parse the contents of CVS/Root to figure it out, but
> it adds complexity that isn't really necessary.
Ok, after looking at it a few minutes it kind of looks like the above script
runs IN the vim editor, and a little searching turns up
cvscommand.vim, cvsvimdiff and cvsmenu.vim. Would any of those make
it so you could retire your RCS script when editing files managed by CVS?
BTW wow, I never new there was such a resource for vim ... but I think for
code editing I will stick with Xemacs.
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter