On 28/02/09 03:44, Markus Heidelberg wrote: > Tony Mechelynck, 27.02.2009: >> On 27/02/09 04:04, Bram Moolenaar wrote: >>> How about some documentation? So that we know how it's supposed to >>> work. >> Yes: the announced eval.txt diff was not included. That's actually a >> good point, because as long as your patch doesn't make it into "official >> Vim", you shouldn't touch the official Vim documentation. Why? Because >> whenever runtime files are updated, the update will sync the user's >> $VIMRUNTIME/doc/ with the _official_ >> ftp://ftp.vim.org/pub/vim/runtime/doc/ and ruthlessly eliminate any >> nonstandard changes you made. Publish your documentation as a separate >> help file, which can be dropped (on any platform) into >> $VIM/vimfiles/doc/ or (on Windows) into ~/vimfiles/doc/ or (on Unix) >> into ~/.vim/doc/, where (in all three cases), runtime upgrade won't >> touch it. > > This workaround with a separate file is not needed if you use the > vim_extended git repository. > > Markus
You cannot expect that all _users_ of your patches will use it. I don't, for one, and I bet I'm not alone of my case. So, if you want to distribute your plugin to _any_ Vim users, you cannot afford to make any changes in the official runtimes (including the official help) for the reasons I mentioned: any user doing a runtime upgrade (by one of the conventional methods such as e.g. rsync with ftp.nluug.nl::Vim/runtime/ or ftp from ftp://ftp.vim.org/pub/vim/runtime/), will immediately lose all your changes to $VIMRUNTIME/**/*. Best regards, Tony. -- God is not dead! He's alive and autographing bibles at Cody's --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
