rneovim.git/runtime/autoload/remote, branch v0.1.2

Fix UpdateRemotePlugins fails problem

2015-12-09T15:09:55+00:00

host.vim: expand $MYVIMRC. #3342

2015-09-15T01:59:13+00:00

According to the vim helpfile:

> fnamemodify({fname}, {mods})
>    ...
>    Note: Environment variables don't work in {fname}, use
>    expand() first then.

So this causes issues if your $MYVIMRC contains environment variables
(e.g. $XDG_CONFIG_HOME)

python: remove current working directory from path

2015-09-14T10:06:49+00:00

Before, running Nvim in a directory containing a Python module `neovim`,
or one that is imported by it or a plugin, will load that module and not
the system one. So Nvim might be tricked into running arbitrary scripts
from the current working directory.

Fixes #1665
Fixes #2530

rplugin: Don't error if plugin is registered before host #2961

2015-07-10T20:11:13+00:00

This makes it possible to register a lazy loaded host in a plugin/ file.
Previously this caused an error on restart after :UpdateRemotePlugins

rplugin: pass additional info to host factory function #2920

2015-07-03T16:12:21+00:00

rplugin: allow users to register hosts #2896

2015-06-25T23:01:38+00:00

remote#host#RequirePythonHost: fix reference to log

2015-06-09T07:29:46+00:00

I could not find a reference to NVIM_PYTHON_PYTHON_LOG anywhere, and
python-client looks for NVIM_PYTHON_LOG_FILE.

~/.nvimlog appears to be hardcoded and enabled by default.  This would
need to be adjusted when this changes.

rplugin: Improve remote plugins detection messages #2769

2015-05-31T16:47:54+00:00

Add if_python3 support

2015-04-20T21:20:23+00:00

Reviewed-by: Michael Reed , Daniel Hahler 
Helped-by: Daniel Hahler

runtime: Handle failures while loading individual remote plugins

2015-04-13T20:21:28+00:00

The s:RegistrationCommands functions will now test the type of the "specs" rpc
call. If it's not a list, then the plugin failed to load and is skipped