I've also thought about parallel fetching, and this is the result:
What about parallel installation, fetching, activation, ... ~
Possible problems:
- activation order could be important, the plugin manager eventually does not
know (yet)
- Vim itself does not allow parallel processing, thus this make VAM depend on
external tools such as parallel, python or the like. It has been a design
choice to keep things simple (VimL only).
- While loading plugins at runtime works mostly it does not work always, thus
installing a plugin and activating it later might change behaviour. And that
has been a design choice that you can trust (as much as possible) that the
result of a VAM installation behaves the same. (no version locking yet, I
know - if you need it create a github bug)
- parallel updating can be implemented trivially, eg using shell scripting:
for git in ~/.vim/vim-addons/*/*.git; do
cd $(dirname $git); git pull &
done
To proberly fix this something else than VimL should be used IMHO, and
that would come with its own problems. Adding '&' to each command would
be trivially (to run git pull in background), but then you would not
have a log to review (the way it is now) - and you would not know when
Vim is done.
Marc Weber
--
--
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
