diff options
| author | Thiago de Arruda <tpadilha84@gmail.com> | 2014-02-20 23:21:01 -0300 | 
|---|---|---|
| committer | Thiago de Arruda <tpadilha84@gmail.com> | 2014-02-20 23:21:01 -0300 | 
| commit | e78a825350b9565549b112279f1d62ba100fb8e7 (patch) | |
| tree | 0379b96c02b2503e47b1b916979cf97fa69133ee | |
| parent | a55e03d4fd8acde9ff8f0a35758ed9c41009c241 (diff) | |
| download | rneovim-e78a825350b9565549b112279f1d62ba100fb8e7.tar.gz rneovim-e78a825350b9565549b112279f1d62ba100fb8e7.tar.bz2 rneovim-e78a825350b9565549b112279f1d62ba100fb8e7.zip | |
Set language of first json-rpc block
| -rw-r--r-- | README.md | 4 | 
1 files changed, 2 insertions, 2 deletions
| @@ -92,7 +92,7 @@ This is how the new plugin system will work:  Here's a sample plugin session using [json-rpc](http://www.jsonrpc.org/specification) (jsonrpc version omitted): -``` +```js  plugin -> vim: {"id": 1, "method": "listenEvent", "params": {"eventName": "keyPressed"}}  vim -> plugin: {"id": 1, "result": true}  vim -> plugin: {"method": "event", "params": {"name": "keyPressed", "eventArgs": {"keys": ["C"]}}} @@ -131,7 +131,7 @@ The difference between plugins and GUIs is that plugins will be started by  neovim, where GUIs will start neovim(or perhaps attach to a running session).  Here's a sample diagram of the process tree: -```txt +```  GUI program    |    ---> Neovim | 
