>Does neobundle allow loading a plugin immediately? >Eg for VAM there are special options such as "load-now" so that you can >even force loading the plugin/* files in .vimrc. Usual Vim behavior is >load all plugin/* files after .vimrc has been processed by Vim. >It is useful in some cases.
It seems be :NeoBundleSource command. It loads all lazy loaded plugins. >> Sorry, I don't want to do it... >Before either of us spends a lot of time I'd like to think about what >the perfect goal would be. Maybe we can agree on a common set of >important features and implement it. This does not mean that you have to >do all work. But I'd like to have shared future. I think the first step is "collaborate with Shougo's NeoBundle" in VAM-kr. If the project is success, you can use neobundle easily. >> What's the "fixing Vim" means? >> I think plugin managers are important. But I don't know about "fixing Vim". >See here about a list of things I think should be improved one day: >http://vim-wiki.mawercer.de/wiki/topic/in-which-way-does-vim-suck.html >I even think about crowd-funding such improvements. However I'm still >stuck at the "language". Even Bram said implementing higher level code >in C is tough. C++ seems natural, But I'd like to think about a new >language which can be used to share code for both: Vim,Emacs and more >editors. I'm not done yet. OK. I get it. It may be interesting suggestion. But it is a waste of time. It divides our community, needs our time, breaks compatibilities. I don't want to make another editor. I loves Vim(and VimL). You should solve other problems in Vim todo list. >Maybe we can even think about giving up both: VAM and neobundle and >create a new plugin manager which serves everybody. But in order to >judge we need a list of features we really care about. >(-> http://vim-wiki.mawercer.de/wiki/topic/neobundle-vs-vam-merge) OK. I will check it. >I meant that emulating will be a substitute. Since NeoBundle and VAM both have >unique features so neither can emulate the other. Emulating NeoBundle in VAM >won't be the real NeoBundle, as emulating VAM in NeoBundle wouldn't be the >real VAM. I agree. I don't want to emulate VAM. But I want to use VAM-kr repository Information. >Vim's website is not very userfriendly. As you said the plugin managers aren't >clearly mentioned. >Built-in synchronous handling would be great. Yes. It is great. But it is too hard to implement. So, I want to add timer feature in Vim. This feature is already in todo list. >> Major point is the embedding of vim, which seems very hard to do, it's on >> the vim wishlist for ages. >Please read the section about yzis (use wiki's search feature). >yzis was about that, and they finally gave up. Yes. So, "new another editor like Vim" or "fork Vim" is a waste of time. Vim's features are huge. >Blindly patching Vim is the wrong thing to do. There are many items to >be considered. Starting to collect those is the right thing to do. I don't understand it... >> Thinking about it... can't support you with money, but testing and >> development are possible. C is a long time ago for me. >I'm not interested in coding C. Too low level. I want at least type >classes (C++ or Haskell like) etc. The language is not problem. But Vim's code is too old. Yes. In other thread, Mr.Bram wants to rewrite Vim by Zimbu sometime. We should respect the thought of Mr.Bram. I can learn Zimbu language for Vim. -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
