Philip Prindeville wrote: > Ben Schmidt wrote: >>> once logged into >>> Sourceforge, it says that this is for filing bugs against the vimonline >>> website... not for filing bugs against Vim itself >>> >> I think that is correct. The procedure for reporting Vim bugs is documented >> in >> Vim's help at, funnily enough >> >> :help bugs >> >> Cheers, >> >> Ben. >> > > Equally funny is that once I have it built and running enough to be able > to do that, I'll probably have fixed the bug myself and it will be a > non-issue at that point.
Even if you fix the bug yourself, you should let others benefit from it, e.g. by sending the bug description and the fix (as a context diff of every file you changed) to Bram and also (if different) to the maintainer(s) of the concerned source(s) (see my previous post), and possibly also to the vim_dev group. Of course, before doing that, you should make sure that you have the latest sources with all patches, and the latest runtimes. See, among others, my HowTo pages: (Unix) http://users.skynet.be/antoine.mechelynck/vim/compunix.htm (Win32) http://users.skynet.be/antoine.mechelynck/vim/compile.htm Best regards, Tony. -- ... Logically incoherent, semantically incomprehensible, and legally ... impeccable! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
