On Fri, Nov 21, 2008 at 12:25:23AM -0800, Tom Link wrote: > > > That sounds interesting. Having to say "to use this plugin, you have > > to install the following 4 vimballs", as I'm currently doing, does not > > seem to be the right way. > > @Marc Weber: > Does your installer provide some sort of version management? To me > this sounds a little bit like Windows installers vs. linux/bsd-type of > package management. I'm not sure how this should look like. Can you give me an example?
Are you talking about changing call a#b#foo() to a#b#version0_1#foo() ? So that you'll end up having a#b#version0_1.vim a#b#version0_2.vim a#b#version0_3.vim a#b#version0_4.vim > I guess I'd much rather prefer dependency handling (ie automatic > downloading & installation of dependencies) in vimball. Is this because you've used vimball a lot of times before? Of course I'd like to use "my tools" I've been using for years as well. Have you actually tried installing one of those installers? If you don't trust me run strace -o /tmp/trace -f vim, then soucre the file. This way you can lookup all files which have been modified. (I'm not sure wether it works on windows yet..) Tom, if you really want to help make me understand the features of vimball you like and you need which are lacking in my installer. You can install each "package" to another directory so that you can remove that easily if you don't like the script. What else do you really need? You'll be notified for updates *before* files are overridden. So you can't loose data. So give it a try and give some feedback so that we can choose the best tool to enhance. But I'd like to see more than just "I'd prefer vimball for no obvious reasons because I feel so".. I'm willing to clean up my library and adopt it to community needs.. But I'll only start to do so if there is valuable feedback because I don't have time to waste either. If I've missed the point retell me. I"ll try to improve to get it the first time in the future. > I think one reason for this is that there was no autoload facility > prior to vim7. A second reason probably is the lack of automatic > dependency handling. It's there you just have to try it once. I even have implemented a proof of concept to download missing files if you just tell vim to get all dependencies of file X based on autoload functions.. Of course if you have function foo() if false call a#b#c() else call d#e#f() endif endfun a/b.vim and d/e.vim will be downloaded.. There is no way for the script to know.. By the way if we manage to separate the user interface from the implementation we can also implement kind of garbage collector removing no longer referenced files. That's what nixos is doing with packages and its the only way to go (IMHO).. Sincerly Marc Weber --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
