On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg <[EMAIL PROTECTED]> wrote:
>> Markus, please put the attached file into the git repo. > > In which branch, master? Yes. That way, everyone will be able to see the README. > I already have plans to split the readme part on the gitweb interface > into two: one for the most simple use of just the master branch as > already done and another for creation of an own branch merging various > feature branches as you did in the attached file. Ah, OK. Feel free to merge/discard my version. Or we can work on one together. Whichever you prefer. > But I'd like to keep it short, forgoing all the things that aren't > special for vim_extended like details in configuring Vim and setting up > git. There is already enough documentation out there, a Vim novice won't > use vim_extended anyway, a git novice though. Well, a git novice might not know about the color.ui option and it really _does_ make working with git easier. I have no problem dumping it, though. > I wonder if it is better to activate the features by default. The Lua > interface for example. I think it is, nobody wants to merge the lua > branch for not using it, do you agree? Why not offer a mergeall branch or something? Personally, I cherry-pick the interesting (to me) stuff, but others might prefer to just build the whole beast. We would then have three parts in the docs: Vanilla, Cherry & All. > I also think it would be better to patch src/auto/configure, then "make > -C src autoconf" wouldn't be necessary anymore. This would also be the > case, when the patch was integrated into mainline. Agreed. Richard --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
