Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syscall.CallAsync should use vim8 job support if available #184

Closed
dbarnett opened this issue Mar 25, 2017 · 0 comments
Closed

Syscall.CallAsync should use vim8 job support if available #184

dbarnett opened this issue Mar 25, 2017 · 0 comments
Assignees

Comments

@dbarnett
Copy link
Contributor

Vim 8 added a native "job" feature to start processes and communicate with them (http://vimhelp.appspot.com/channel.txt.html). Syscall.CallAsync should use that mechanism under the hood in vim instances where it's available for more robust async support with fewer caveats.

@dbarnett dbarnett self-assigned this Mar 25, 2017
dbarnett added a commit that referenced this issue Apr 15, 2017
Enhances Syscall.CallAsync to invoke syscalls as native vim jobs if the vim instance supports them, and demotes the clientserver-based implementation to "legacy" (to be eventually removed in #190).

Resolves #184.
dbarnett added a commit that referenced this issue Apr 24, 2017
Changes since 1.13.0:
  * Add vim job support to Syscall.CallAsync (#184).
  * Add python3 support (#193).
  * Enable native JSON support on neovim (#194).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant