dear Charles E Campbell and stosss:
maybe you can find my answer in to Marc Weber's letter. sorry. i have
something to do this morning. so i don't have much time. if not i will
explain to your question myself. Happy to discuss with you all. Thank
you for your pingback.
2013/3/10 孔晓泉 <u1mail2me@gmail.com>:
> dear Marc Weber:
> yes, i agree some point of your ideal. now let's explain some thing:
> 1. vundle && pathogen
> i read their code and i think their function are quite less.
> why i want write a another manager? because:
> 1.1 some plugin need out of band program to help them, such as ctag,
> package manager should do something on it
> 1.2 some plugin need python support or set nocompatible，but unless you
> read the doc before, you will fall and you don't know why
> 1.3 with the plugin's function is more and more complex, some public
> vim script library have appeared "L9 : Vim-script library", dependency
> will manage
> 1.4 auto-tools and interaction of other programs, let bash write
> package name into your .vimrc is not the good path, at least i don't
> think so.
> 1.5 security, wild plugin on github or something may curse security
> problem, you can't guarantee that. user may write a wrong git address
> that will horrible
> 1.6 copyright , although copyright is not your care, but in law, it is required
> 2. vim-addon-manager
> sorry, that's my fault. but there is too many plugin manager called
> "vim-addon-manager". what i first found it's the ubuntu's package
> called "vim-addon-manager" which is write in ruby. well i don't like
> that, not only you will install ruby for this but also i hate ruby
> things for my personal reason. and it's looks not a good manager in my
> point of view. may be what your means "vim-addon-manager" is this
> http://www.vim.org/scripts/script.php?script_id=2905 or
> https://github.com/MarcWeber/vim-addon-manager which may write by you
> judged by author's name. it's really a good job. it look's a little
> simlar to my job on functions.
> 3. vimapt
> Sentence summary is "apt on vim", this is what i want
>
> If you think different don't be shy and tell me.
>
>
> 2013/3/9 Marc Weber <marco-oweber@gmx.de>:
>> Excerpts from 孔晓泉's message of Sat Mar 09 05:42:23 +0100 2013:
>>> hello everyone:
>>> recently i write a new vim package/plugin manager .because it
>>> operate like dbian's apt, so i call it "vimapt".
>>> here is the repository https://bitbucket.org/howlanderson/vimapt
>>> and some article in my blog http://www.howlanderson.net/?cat=33
>>> Notice: vimapt is just in alpha, unstable and may full of bugs
>>> I hope you can try it, whether you think it is good or bad, please
>>> give me some feedback, Thank you very much!
>>
>> Hy 孔晓泉,
>>
>> In the future please write to the mailinglist *before* you start *yet
>> another package* for doing a task. Because there are already many
>> implementations:
>>
>> pathogen
>> vundle
>> vim-addon-manager
>> vimana
>> (and probbably some more)
>>
>> Then give those projects a try, and consider contributing (if they
>> philosophy is close enough to your ideas) - if not - document in which
>> way your solution is different. This will make it easier for other
>> people to know whether they want to give your solution a try
>>
>> Your very last sentence sasy:
>>
>> == Inspiration and ideas from ==
>> vundle
>> pathogen
>> bundler
>> Scott Bronson
>>
>> which clearly shows that you've missed vim-addon-manager, which might be
>> closest to what you've been looking for.
>>
>> Which in turn makes me think we should no longer wait, we have to setup
>> the git based wiki system on www.vim.org ASAP, else this will happen
>> over and over again and split the community.
>>
>> Its great that people around Vim do solve problems - step up and get it
>> done. But the Vim eco system sucks so much - that energy is wasted a
>> lot. And we as community have to fix that.
>>
>> If you think different don't be shy and tell me.
>>
>> Marc Weber
>>
>> --
>> --
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> ---
>> You received this message because you are subscribed to the Google Groups "vim_use" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment