aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/os/event.c
diff options
context:
space:
mode:
authorThiago de Arruda <tpadilha84@gmail.com>2014-06-26 18:10:05 -0300
committerThiago de Arruda <tpadilha84@gmail.com>2014-07-17 11:37:08 -0300
commit887d32e54672cc3957bd2977df92fc3e9de10a52 (patch)
treea092cb21c31fc27e9b3c2ca652aadc73dbcc17c3 /src/nvim/os/event.c
parent0b2b1da0e809e529a25530d80a77284d618390cf (diff)
downloadrneovim-887d32e54672cc3957bd2977df92fc3e9de10a52.tar.gz
rneovim-887d32e54672cc3957bd2977df92fc3e9de10a52.tar.bz2
rneovim-887d32e54672cc3957bd2977df92fc3e9de10a52.zip
provider: New module used to expose extension points for core services
Introducing the concept of providers: co-processes that talk with the editor through the remote API and provide implementation for one or more core services. The `provider_register` function and it's API wrapper can be used by channels that want to self-register as a service provider. Some old builtin vim features will be re-implemented as providers. The `provider_has_feature` function is used to check if a provider implementing a certain feature is available(It will be called by the `has` vimscript function to check for features in a vim-compatible way) This implements the provider module without exposing any extension points, which will be done in future commits.
Diffstat (limited to 'src/nvim/os/event.c')
-rw-r--r--src/nvim/os/event.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/nvim/os/event.c b/src/nvim/os/event.c
index 4e091716b2..0528339865 100644
--- a/src/nvim/os/event.c
+++ b/src/nvim/os/event.c
@@ -9,6 +9,7 @@
#include "nvim/os/input.h"
#include "nvim/os/channel.h"
#include "nvim/os/server.h"
+#include "nvim/os/provider.h"
#include "nvim/os/signal.h"
#include "nvim/os/rstream.h"
#include "nvim/os/job.h"
@@ -50,6 +51,8 @@ void event_init(void)
channel_init();
// Servers
server_init();
+ // Providers
+ provider_init();
}
void event_teardown(void)