On 2008-10-06, Edward Peschko <[EMAIL PROTECTED]> wrote: > all, > > Instead of concentrating on vimdiff startup time, I was wondering, > maybe, if there was a way to view several 'pairs' of files, ie, > instead of: > > vimdiff file1.old file1.new > vimdiff file2.old file2.new > > > I could say: > > vimdiff -f 'filelist' > > and then have filelist contain the pairs of files that I want to view. > Or of course if there was any other mechanism on the command line to > vimdiff multiple sets of files. > > As I see it, this combined with an internal diff (can you statically > link diff, anyways?) would save about 10 secs of startup time per > file, or over an hour if editing 360 files...
Here's an approach I've taken. I somehow select the set of new files I'm interested in and give that list as arguments to vim, e.g., vim $(find . -name \*.new) Then I define a command that diffs the current file against its predecessor, e.g., :command -bar Diff vert diffsplit %:r.old For the first file, I just execute :Diff When I'm done with that one, I execute something like this: :diffoff | wincmd l | only | n | Diff which terminates the first diff, closes the new window, goes to the next file in the argument list, and diffs it against its predecessor. Rather than have to recall that command from the command history for each file, I may bind it to some easy-to-type key I'm not using at the moment, e.g., :nmap <C-N> :diffoff | wincmd l | only | n | Diff<CR> I don't do that very often, so an ad hoc approach like the above works well enough for me. If you that regularly, you may want to define some commands and/or mappings that encapsulate those steps and put them in your ~/.vimrc. Regards, Gary --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
