neovim - Vim-fork focused on extensibility and usability

Age	Commit message (Collapse)	Author	Files
2023-11-28	fix(rplugin): dont create data dir if it's a broken symlink #25726	Samuel (ThinLinc team)	1
	Checking if it's non-empty and not a directory gets us quite far, but not all the way. While a working symlink would trigger the earlier checks, a broken symlink does not. This commit fixes the special case where ~/.local/share/nvim already exists but is a broken symlink. Thus, it fixes the following error on startup: E739: Cannot create directory /home/samuel/.local/share/nvim: file already exists
2022-06-04	fix(startup): nvim with --clean should not load user rplugins	bfredl	1
	runtime rplugins such like legacy script providers are not affected by this change.
2018-12-27	rplugin.vim: Add migration support for Windows, nvim/ -> nvim-data/	James McCoy	1

2018-12-20	Use stdpath() to determine rplugin manifest path	James McCoy	1

2018-01-17	runtime: UpdateRemotePlugins: allow bar (#7865)	zandrmartin	1

2017-03-27	rplugin.vim: GetManifestPath(): be more explicit (#6361)	Daniel Hahler	1

2017-03-11	rplugin: Call s:LoadRemotePlugins() on startup.	Justin M. Keyes	1
	Dispense with the FuncUndefined/CmdUndefined quasi-optimization. If there are no rplugins, plugin/rplugin.vim takes less than 1ms. Closes #5821 Closes #6250 Helped-by: Qiming zhao <chemzqm@gmail.com>
2016-03-10	rplugin: Initialize remote plugins lazily. #4384	Shougo Matsushita	1

2016-02-14	Improve remote plugin scripts	Shougo Matsushita	1

2014-11-21	runtime: Refer to plugins running outside Nvim as "remote plugins"	Thiago de Arruda	1
	- Rename autoload/rpc to autoload/remote - External plugins are now remote plugins - External plugins directory is "rplugin"