| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
: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.
|
| |
|
|
| |
This makes stderr and exit callbacks work for rpc jobs
|
| | |
|
| |
|
|
| |
If the base directory does not exist, let mkdir(...,'p') create it.
|
| |
|
|
|
| |
Without the for-loop it is easier to follow, more explicit, and fewer
lines.
|
| |
|
|
| |
Uses $NVIM_RPLUGIN_MANIFEST if available
|
| | |
|
| | |
|
| |
|
|
| |
Closes #4795
|
| | |
|
| | |
|
| |\
| |
| | |
Ruby remote plugin support
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
This makes it possible to register a lazy loaded host in a plugin/ file.
Previously this caused an error on restart after :UpdateRemotePlugins
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
Reviewed-by: Michael Reed <m.reed@mykolab.com>, Daniel Hahler <github@thequod.de>
Helped-by: Daniel Hahler <github@thequod.de>
|
| |
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
- Rename autoload/rpc to autoload/remote
- External plugins are now remote plugins
- External plugins directory is "rplugin"
|