rneovim.git/runtime/autoload/remote, branch v0.3.7 Neovim fork with Rahm's personal hacks. remote/host.vim: specify {nosuf} for globpath() (#8882) 2018-08-24T08:17:59+00:00 Justin M. Keyes justinkz@gmail.com 2018-08-24T08:17:59+00:00 c0157e8fe0b9b25d9004b3f10a0ef5d33e4ff027 






remote: add node.js as a remote plugin provider
2017-10-29T18:10:33+00:00

Billy Vong
billyvg@gmail.com

2017-10-29T18:10:33+00:00

7890157931a3fdfddb647a06e27346071c55564c












rpc: Don't delay notifications when request is pending (#6544)
2017-10-29T02:06:53+00:00

Björn Linse
bjorn.linse@gmail.com

2017-10-29T02:06:53+00:00

2a3bcd1ff883429a3dd17e7ae5ddc1396abbad17

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




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






escape amatch filename (#7292)
2017-09-19T06:13:44+00:00

Andy Russell
arussell123@gmail.com

2017-09-19T06:13:44+00:00

460aab39509015543aeafcaa4bcc730564793416

Fixes #7046
Fixes autozimu/LanguageClient-neovim#77




Fixes #7046
Fixes autozimu/LanguageClient-neovim#77






rplugin: Call s:LoadRemotePlugins() on startup.
2017-03-11T11:26:22+00:00

Justin M. Keyes
justinkz@gmail.com

2017-03-10T21:01:34+00:00

d1afd434f30202410b217e7137c4a2a4fe055dbe

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>





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>







rplugin: resolve paths in manifest file (#5501)
2016-10-18T21:16:13+00:00

Marco Hinz
mh.codebro@gmail.com

2016-10-18T21:16:13+00:00

657ba62a84de4ae0fd6dbaa2d3c238de4b372669

`: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.




`: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)
2016-10-11T23:04:59+00:00

Shougo
Shougo.Matsu@gmail.com

2016-10-11T23:04:59+00:00

1dde512498d2fa9f3427861b5d4f894c778f992b












doc/vim_diff.txt (#5432)
2016-10-06T07:45:24+00:00

Justin M. Keyes
justinkz@gmail.com

2016-10-06T07:45:24+00:00

d57f25e5ef4a02935e500dcb6cf2f7df45017dca












remote/host.vim: Avoid "No matching autocommands".
2016-08-22T02:03:28+00:00

Justin M. Keyes
justinkz@gmail.com

2016-08-21T20:15:50+00:00

297677ecf42501d2bef45dd4f083002a0963b205

: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.





: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 jobs
2016-08-20T10:55:35+00:00

Björn Linse
bjorn.linse@gmail.com

2016-05-12T20:25:15+00:00

2d60a15e25f487eda1ac00a9e6cdf9a6564fb416

This makes stderr and exit callbacks work for rpc jobs





This makes stderr and exit callbacks work for rpc jobs