@David me saying "you're wrong": You're right. Thanks for facing me.
About APIs:
The main problem is that you cannot just access the gitub api, because
accessing the internet from PHP scripts is not allowed. Code like this
fails: echo file_get_contents('http://google.de');
from #sourceforge its still the case:
15:58 MarcWeber> Eg this doesn't echoe anything: echo file_get_contents('http://google.de');
15:59 @ctsai-sf> That's correct, we do not allow outbound connections due to past abuse.
16:00 @ctsai-sf> We are aware that this is something users want, and we will likely reconsider this periodically,
however there are no plans to change the current behavior in the foreseeable future.
That's why thinking about changing hosting would make
such implementations much easier.
Of course you could setup any SSH based hooks and update missing info by
cron jobs, too. But I somehow dislike adding more and more hacks.
Immediate feedback (such as getting the right plugin title from github)
is user friendly.
That's why Bram should comment and reevaluate the situation.
Anyway, taking care of neovim (and how the community wants to deal with
it) could be very important, too. It might be too early to judge.
Thus what is the wisest way to proceed ?
Start a new project? Unless there is a nice central way to document
options (eg where to find plugins) this all is kind of 'lucky' IMHO.
Also do we want "testing and continuous integration" ?
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/d/optout.
No comments:
Post a Comment