> a#b#version0_1#foo() ? I was just wondering what would happen if you installed package A consisting of
foo.vim (version 2) bar.vim and then installed package B containing the files foo.vim (version 1) boo.vim Then I remember that questions older windows installers used to ask: "Do you really want to overwrite shdkishd.dll with shdkishd.dll". The vimball approach would be to have three separate packages A, B, and foo. If you wanted to update foo, you wouldn't have to touch packages A and B. With your approach, you'd have to update the installers for A and B. But maybe I got it all wrong and maybe there is an obvious solution for that. And maybe such questions would become obsolete anyway with the use of git. One thing though. You use start and end markers. How do you protect against end markers accidentally showing up in the file? Vimball uses line counts for this. One solution would be to insert a finish statement after the loader and to not comment out the markers, I guess. IMHO line counts could help to simplify the loader though because you could then simply use getline(from, from + count) to extract the file contents. I'll check your libraries out. BTW I took the liberty to re-implement your outline.vim in ttoc[1], which does some dynamic filtering. [1] http://www.vim.org/scripts/script.php?script_id=2014 --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
