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

Support Vim 8’s built-in async and timers #151

Open
roryokane opened this issue Sep 13, 2016 · 2 comments
Open

Support Vim 8’s built-in async and timers #151

roryokane opened this issue Sep 13, 2016 · 2 comments

Comments

@roryokane
Copy link

roryokane commented Sep 13, 2016

Vim 8.0 was released yesterday, and its new features include background jobs, timers, and asynchronous I/O using channels.

Your description for the g:easytags_async option says that async isn’t the default yet because you’re not sure if it will work reliably for everybody. If you change easytags.vim to use Vim’s new built-in functions such as job_start(), the async tag generation would be more likely to be reliable. Then you could finally make it the default, providing a smoother experience for all users.

You could also add ang:easytags_on_timer option, if you think there would be a demand for it. Though personally I think async would be all I need.

However, you probably shouldn’t remove the current synchronous and hacky-async methods until enough people have had the chance to upgrade to Vim 8.

@jalcine
Copy link

jalcine commented Apr 4, 2017

Doing a very quick scan of the code, it looks like a lot of the logic for generating tags is here. This would be an undertaking looking at the subtle differences of neovim and vim8's approaches to job control / channels.

@Taverius
Copy link

Taverius commented May 24, 2017

async.vim exists, so that should simplify things.

It doesn't have fallback to non-8 vim sync, but that's already built in here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants