I might have been drinking too much coffee lately, but I had hard time to understand what the .... have these guys done in their overlay with a certain ebuild version. The problem was that every time I did: vimdiff /usr/{local/overlays/_the_guys,portage}/net-dns/djbdns/djbdns-1.05-r15.ebuild vim was creating a new djbdns-1.05-r15.ebuild in /usr/portage/... because I was using gentoo-syntax. So is there any way to NOT create an example ebuild when called from {g,}vimdiff, but an empty file insted? Reproducible: Always Steps to Reproduce: 1. /usr/{local/overlays/_the_guys,portage}/net-dns/djbdns/djbdns-1.05-r15.ebuild Actual Results: A new ebuild is created (because at this time -r15 is not available in /usr/portage). This makes it useless to try to understand diffs between an existing file and just created-on-the-fly ebuild. Expected Results: Instead, create a new file (when called from {g,}vimdiff at least). It would be better if the diff mode in vim is used (so that it will work with vim -d ebuild1 ebuild2), but might be more difficult?
added g:ebuild_create_on_empty option to toggle new ebuild creation on/off on a new ebuild. This will make the next release and is in subversion. plugin/newebuild.vim: if !exists("g:ebuild_create_on_empty") " Enable autogeneration of ebuilds by default let g:ebuild_create_on_empty = 1 endif augroup NewEbuild au! autocmd BufNewFile *.e{build,class} \ if g:ebuild_create_on_empty | \ call <SID>MakeNewEbuild() | \ endif augroup END
