kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-23 20:55:18 -07:00
Code Issues Packages Projects Releases Wiki Activity

Set language of first json-rpc block

Browse Source
This commit is contained in:
Thiago de Arruda 2014-02-20 23:21:01 -03:00
parent a55e03d4fd
commit e78a825350
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -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): 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"}} plugin -> vim: {"id": 1, "method": "listenEvent", "params": {"eventName": "keyPressed"}}
vim -> plugin: {"id": 1, "result": true} vim -> plugin: {"id": 1, "result": true}
vim -> plugin: {"method": "event", "params": {"name": "keyPressed", "eventArgs": {"keys": ["C"]}}} 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). neovim, where GUIs will start neovim(or perhaps attach to a running session).
Here's a sample diagram of the process tree: Here's a sample diagram of the process tree:
```txt ```
GUI program GUI program
| |
---> Neovim ---> Neovim