| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | test: remote/define.vim: range | Case Nelson | 2016-04-18 |
| | | |||
| * | remote/define.vim: support remote function "range" | Paul Jolly | 2016-04-18 |
| | | |||
| * | Fix loading remote plugin error | Shougo Matsushita | 2016-04-19 |
| | | |||
| * | rplugin: Ignore modeline while chaining events | Dan Elkouby | 2016-04-18 |
| | | |||
| * | rplugin: Fix wrong condition for lazy loading remote plugins | Aleksei Khudiakov | 2016-03-31 |
| | | |||
| * | Merge pull request #4410 from alexgenco/ruby_rplugin | Justin M. Keyes | 2016-03-11 |
| |\ | | | | | Ruby remote plugin support | ||
| | * | Ruby remote plugin support | Alex Genco | 2016-03-10 |
| | | | |||
| * | | rplugin: let the python host identify packages | Björn Linse | 2016-03-11 |
| | | | |||
| * | | rplugin: Silence :doautocmd. #4384 | Justin M. Keyes | 2016-03-11 |
| |/ | |||
| * | rplugin: Initialize remote plugins lazily. #4384 | Shougo Matsushita | 2016-03-10 |
| | | |||
| * | Improve remote plugin scripts | Shougo Matsushita | 2016-02-14 |
| | | |||
| * | Fix UpdateRemotePlugins fails problem | Shougo Matsushita | 2015-12-10 |
| | | |||
| * | host.vim: expand $MYVIMRC. #3342 | Jonathan Skeate | 2015-09-14 |
| | | | | | | | | | | | | | 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 | Jakob Schnitzer | 2015-09-14 |
| | | | | | | | | | | | 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 | Björn Linse | 2015-07-10 |
| | | | | | | 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 | Nick Hynes | 2015-07-03 |
| | | |||
| * | rplugin: allow users to register hosts #2896 | Nick Hynes | 2015-06-25 |
| | | |||
| * | remote#host#RequirePythonHost: fix reference to log | Daniel Hahler | 2015-06-09 |
| | | | | | | | | | 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 | Shougo Matsushita | 2015-05-31 |
| | | |||
| * | Add if_python3 support | Shougo Matsushita | 2015-04-21 |
| | | | | | | Reviewed-by: Michael Reed <m.reed@mykolab.com>, Daniel Hahler <github@thequod.de> Helped-by: Daniel Hahler <github@thequod.de> | ||
| * | runtime: Handle failures while loading individual remote plugins | Thiago de Arruda | 2015-04-13 |
| | | | | | | 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 | ||
| * | Improve Python host messages. | Florian Walch | 2014-11-26 |
| | | |||
| * | Print an error and exit when there are no plugins. | Bjorn Tipling | 2014-11-24 |
| | | | | | | | | | | Issue: #1537 Running the :UpdateRemotePlugins command will show an ugly, unhelpful error when no plugins were found. This change has neovim print an error message and does not attempt to start the python-client which requires at least one plugin. | ||
| * | runtime: Refer to plugins running outside Nvim as "remote plugins" | Thiago de Arruda | 2014-11-21 |
| - Rename autoload/rpc to autoload/remote - External plugins are now remote plugins - External plugins directory is "rplugin" | |||