| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
On some versions of macOS, pbcopy doesn't work in tmux <2.6
https://superuser.com/q/231130
Fallback to tmux in that case.
Add a healthcheck for this scenario.
|
|
|
|
|
|
|
|
|
|
|
| |
The argument expansion for :Man depends on the number of arguments given to it
starting at the command itself. But user completion functions always provide the
entire command-line which can include modifier commands like :tab, :vert, etc.
leading to a wrong number of arguments.
Prune all arguments up to :Man.
Fixes #7872.
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
Closes #7772
|
|/
|
|
|
|
|
| |
Check that the full path to the python interpreter starts with
$VIRTUAL_ENV.
closes #7770
|
| |
|
|
|
|
|
|
|
|
|
| |
For back-compat, :CheckHealth runs :checkhealth. But don't define
:CheckHealth explicitly, it adds noise to wildmenu completion.
Completion of healthchecks doesn't yet work with :checkhealth, this is
a regression but it needs to be implemented for :checkhealth rather than
keeping :CheckHealth around.
|
|
|
|
|
|
|
|
| |
vim-patch:8.0.1206: no autocmd for entering or leaving the command line
(commit a4f6cec7a31ff8dbfa089b9e22227afbeb951e9b)
NA patches:
vim-patch:8.0.0320: warning for unused variable with small build
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ci: install nodejs 8 in Appveyor, Travis
provider: check node version for debug support
Resolve https://github.com/neovim/neovim/pull/7577#issuecomment-350590592 for Unix.
provider: test if nodejs in ci supports --inspect-brk
nodejs host for neovim requires nodejs 6+ to work properly.
nodejs 6.12+ or 7.6+ is required for debug support via `node --inspect-brk`.
provider: run cli.js of nodejs host directly
npm shims are useless because the user cannot set node to debug mode via
--inspect-brk. This is problematic on Windows which use batchfiles and
shell scripts to compensate for not supporting shebang.
The patch uses `npm root -g` to get the absolute path of the global npm
modules. If that fails, then the user did not install neovim npm package
globally. Use that absolute path to find `neovim/bin/cli.js`, which is
what the npm shim actually runs with node. glob() is for a simple file
check in case bin/ is removed because the npm shims are ignored now.
|
|
|
|
|
|
|
|
|
|
|
| |
ruby uses batchfiles with 'cmd' extension.
gem creates batchfiles with 'bat' extension.
`gem install rails` does the following in Windows (not Cygwin):
1. Run `gem.cmd install rails` on cmd.exe
2. gem.cmd runs `ruby.exe -x gem install rails`
3. `rails` gem is installed.
`rails.bat` is created in the same directory
where ruby.exe and gem.cmd reside.
|
|
|
|
|
|
|
| |
This change exposed a memory issue with buffered channels, possibly
involving GC. Revert until it has been fixed.
This reverts commit 0de019b6a65c6dd5141b7e002343df3689065ce7.
|
| |
|
|
|
|
|
|
|
| |
neovim-ruby-host is a ruby script.
neovim-node-host is a shell script.
Both don't work in cmd.exe so gem and npm provide batchfile shims.
Return the full path of these shims, cmd.exe knows better what to do with these files.
|
|
|
|
|
|
|
| |
Fix bug that checked for npm AND yarn, where we wanted npm OR yarn.
But since we call `npm` exclusively, and it's highly unlikely you have
yarn installed without npm, let's just remove the yarn check altogether.
Addresses https://github.com/neovim/node-client/issues/41
|
| |
|
|
|
|
| |
fixes #7527
fixes #7536
|
|
|
|
|
| |
:checkhealth reports that remote plugins are unregistered
after running :UpdateRemotePlugins because of the backslashes in filepath.
Normalize them to forward slashes because the paths in rplugin.vim are normalized in autoload/remote/host.vim.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Update runtime files.
https://github.com/vim/vim/commit/b0d45e7f5354375edd02afafde3bd37dac1515ff
|
| |
| |
| |
| |
| |
| | |
Long overdue runtime update.
https://github.com/vim/vim/commit/01164a6546b4c635daf96a1f17d1cb2d07f32a66
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: Ignored changes to matchit.vim in favor of faca81411628.
---
Update runtime files.
https://github.com/vim/vim/commit/37c64c78fd87e086b5a945ad7032787c274e2dcb
|
| |
| |
| |
| | |
Fixes #6664 until #6272 is merged and sdtpath('data') can be used.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Update runtime files. Add Rust support.
https://github.com/vim/vim/commit/3c2881dc1195f53ebafc387378399ddd6cb677a7
|
| |
| |
| |
| | |
ref #7473
ref #7490
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Runtime file updates.
https://github.com/vim/vim/commit/214641f77df6f318a4b3a0b09723c19859a103f4
N/A:
vim-patch:26a280c47a1c
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the old behavior, if a GUI makes a blocking request that requires user
interaction (like nvim_input()), it would not get any screen updates.
The client, not nvim, should decide how to handle notifications during a
pending request. If an rplugin wants to avoid async calls while a sync call is
busy, it likely wants to avoid processing async calls while another async call
also is handled as well.
This may break the expectation of some existing rplugins. For compatibility,
remote/define.vim reimplements the old behavior. Clients can opt-out by
specifying `sync=urgent`.
- Legacy hosts should be updated to use `sync=urgent`. They could add a flag
indicating which async methods are always safe to call and which must wait
until the main loop returns.
- New hosts can expose the full asyncness, they don't need to offer both
behaviors.
ref #6532
ref #1398 d83868fe9071af1b4866594eac12f7aa0fa71b53
|
| |
|
|
|
|
| |
This allows us to remove :CheckHealth later (avoids wildmenu noise).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
`:syntax keyword` is affected by 'iskeyword'. When we aligned
'iskeyword' to that of filetype=help, colon (:) is now included.
Simplest way to deal with this is to include colon (:) in the `:syntax
keyword` directive.
Also:
- change "SUGGESTIONS" mouthful to "ADVICE"
- change "SUCCESS" to "OK"
|
| |
|
|
|
|
| |
Fixes #7046
Fixes autozimu/LanguageClient-neovim#77
|
|
|
|
|
|
|
|
| |
Always check for the presence of pyenv_root if pyenv is installed: if it
is not set, we don't know if it was intentional. If it wasn't
intentional, the warning is confusing (see #7176).
closes #7176
|