aboutsummaryrefslogtreecommitdiff
path: root/runtime/autoload/remote
Commit message (Collapse)AuthorAge
* rplugin: resolve paths in manifest file (#5501)Marco Hinz2016-10-18
| | | | | | | `:CheckHealth nvim` would always report an outdated manifest if symlinks were used, because the manifest file contains unresolved paths that get compared against resolved paths. Now we resolve paths before they get written to the manifest file.
* UpdateRemotePlugins: Discard duplicate paths. (#5464)Shougo2016-10-12
|
* doc/vim_diff.txt (#5432)Justin M. Keyes2016-10-06
|
* remote/host.vim: Avoid "No matching autocommands".Justin M. Keyes2016-08-21
| | | | | | | :silent does not silence this message, even :redir does not consume it. But execute() _does_ consume it, which interferes with the current implementation of health.vim. It's prudent to avoid it in any case, even if the implementation of health.vim changes in the future.
* job control: reuse common job code for rpc jobsBjörn Linse2016-08-20
| | | | This makes stderr and exit callbacks work for rpc jobs
* host.vim: s:GetManifestPath(): octal permissionsJustin M. Keyes2016-08-17
|
* host.vim: s:GetManifestPath(): Create base directory if needed.Justin M. Keyes2016-08-17
| | | | If the base directory does not exist, let mkdir(...,'p') create it.
* host.vim: s:GetManifestPath(): Remove for-loop.Justin M. Keyes2016-08-17
| | | | | Without the for-loop it is easier to follow, more explicit, and fewer lines.
* runtime: rplugin manifest written to $XDG_DATA_HOMETommy Allen2016-08-17
| | | | Uses $NVIM_RPLUGIN_MANIFEST if available
* eval.c: rename capture() to execute() (#5132)Justin M. Keyes2016-07-31
|
* rplugin: Manifest file name fallback (#4935)Shougo2016-06-30
|
* host.vim: s:RegistrationCommands(): Normalize slashes.Justin M. Keyes2016-05-22
| | | | Closes #4795
* test: remote/define.vim: rangeCase Nelson2016-04-18
|
* remote/define.vim: support remote function "range"Paul Jolly2016-04-18
|
* Fix loading remote plugin errorShougo Matsushita2016-04-19
|
* rplugin: Ignore modeline while chaining eventsDan Elkouby2016-04-18
|
* rplugin: Fix wrong condition for lazy loading remote pluginsAleksei Khudiakov2016-03-31
|
* Merge pull request #4410 from alexgenco/ruby_rpluginJustin M. Keyes2016-03-11
|\ | | | | Ruby remote plugin support
| * Ruby remote plugin supportAlex Genco2016-03-10
| |
* | rplugin: let the python host identify packagesBjörn Linse2016-03-11
| |
* | rplugin: Silence :doautocmd. #4384Justin M. Keyes2016-03-11
|/
* rplugin: Initialize remote plugins lazily. #4384Shougo Matsushita2016-03-10
|
* Improve remote plugin scriptsShougo Matsushita2016-02-14
|
* Fix UpdateRemotePlugins fails problemShougo Matsushita2015-12-10
|
* host.vim: expand $MYVIMRC. #3342Jonathan Skeate2015-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 pathJakob Schnitzer2015-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 #2961Björn Linse2015-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 #2920Nick Hynes2015-07-03
|
* rplugin: allow users to register hosts #2896Nick Hynes2015-06-25
|
* remote#host#RequirePythonHost: fix reference to logDaniel Hahler2015-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 #2769Shougo Matsushita2015-05-31
|
* Add if_python3 supportShougo Matsushita2015-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 pluginsThiago de Arruda2015-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 Walch2014-11-26
|
* Print an error and exit when there are no plugins.Bjorn Tipling2014-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 Arruda2014-11-21
- Rename autoload/rpc to autoload/remote - External plugins are now remote plugins - External plugins directory is "rplugin"
generated by cgit (git 2.34.1) at 2025-08-05 14:42:44 +0000