~neovim-ppa/neovim-ppa/python-neovim : changes

~neovim-ppa/neovim-ppa/python-neovim » Changes from revision 334

From Revision 48 to 29

Rev	Summary	Authors	Tags	Date
48	Merge pull request #20 from tarruda/fix-next_message-error-h... Merge pull request #20 from tarruda/fix-next_message-error-handling Process all messages before throwing EOF errors	Thiago de Arruda		10 years ago
47	Merge pull request #19 from tarruda/more-optimizations Merge pull request #19 from tarruda/more-optimizations More optimizations	Thiago de Arruda	0.0.9	10 years ago
46	Merge pull request #17 from tarruda/refactor-concurrency Merge pull request #17 from tarruda/refactor-concurrency Refactor concurrency model	Thiago de Arruda	0.0.8	10 years ago
45	Merge pull request #15 from equalsraf/tb-vim-dir Merge pull request #15 from equalsraf/tb-vim-dir Update default paths in test_runtime_paths	Thiago de Arruda		10 years ago
44	Bump version Bump version	Thiago de Arruda	0.0.7	10 years ago
43	Implement PluginHost and ScriptHost classes Implement PluginHost and ScriptHost classes - Fix UvStream for stdin/stdout transport - Add logging messages for easier debugging through NEOVIM_PYTHON_LOG_FILE environment variable - Add profiling through the NEOVIM_PYTHON_PROFILE environment variable - Fixed more python-vim bridge compatiblity issues - Add a vim_compatible option to transform numbers resulting from `vim.eval` into strings - Add vim.timeout to represent `next_message` timeouts errors. - Add tests for the PluginHost This enables usage of the python client as a plugin host for Neovim, enabling limited support for python plugins developed for vim. An additional feature is provided: Modules under 'pythonx' added to runtime directories are automatically loaded if the name starts with 'nvim_'. Such modules must implement a class with name starting with 'Nvim'. Implementations can use the __init__ method to listen for Neovim events and provide implementation for core services. Right now this feature is still limited, but here is an example: https://gist.github.com/tarruda/42f5236449857278f911	Thiago de Arruda		10 years ago
42	Bump version Bump version	Thiago de Arruda	0.0.6	10 years ago
41	Add support for client-side RPC Add support for client-side RPC A major refactor was necessary in order to support client-side RPC: - Every API function now has a non-blocking variant(prefixed with `send_`). These send_* functions return promises that have a single `wait` method to wait for the result. - The synchronous versions are still provided, but are implemented by calling the async version followed by a `wait` call. - `vim.next_event` is now `vim.next_message`, and messages are specialized objects that represent events or requests. It always has at least three properties: `name`, `arg` and `type` where: - `name` is the method/event name - `arg` is the method/event arguments - `type` is either `event` or `request` Additionally, requests have a `reply` method that can be used respond to the request. The `reply` method accepts a single argument that will be returned to the remote nvim instance. - `vim.push_event` is now `vim.push_message` and receives two arguments: `name` and `arg`. - Multi-thread synchronization was refactored/improved On top of that, the `expect` method was removed since that can be easily implemented as a higher-level feature of a test library.	Thiago de Arruda		10 years ago
40	Make sure libuv event loop is paused on all events Make sure libuv event loop is paused on all events	Thiago de Arruda		10 years ago
39	Add the VimError class as an attribute of the vim object Add the VimError class as an attribute of the vim object	Thiago de Arruda		10 years ago
38	Bump version Bump version	Thiago de Arruda	0.0.5	10 years ago
37	Never stop reading data in the UvStream class Never stop reading data in the UvStream class Even in the middle of a `write` call, we should always be prepared to read/queue data to avoid deadlocks with nvim's process.	Thiago de Arruda		10 years ago
36	Implement push_event method to enable event loop integration Implement push_event method to enable event loop integration	Thiago de Arruda		10 years ago
35	Refactor core functions to enable thread-safety in the API Refactor core functions to enable thread-safety in the API - Remove lazy initialization of helper properties - Add 'interrupt' method to the stream class, which allows other threads to call API functions while another one is blocking on `next_event` - Synchronize access to `next_event`/`msgpack_rpc_call`	Thiago de Arruda		10 years ago
34	Merge pull request #6 from Mause/patch-1 Merge pull request #6 from Mause/patch-1 Correct typo	Thiago de Arruda		10 years ago
33	Merge pull request #5 from eminence/master Merge pull request #5 from eminence/master Fix example in README	Thiago de Arruda		10 years ago
32	Add event broadcast tests Add event broadcast tests	Thiago de Arruda		10 years ago
31	Fix assertion in next_event Fix assertion in next_event	Thiago de Arruda		10 years ago
30	Bump version Bump version	Thiago de Arruda	0.0.4	10 years ago
29	Add support for server events Add support for server events	Thiago de Arruda		10 years ago