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

Async work indicator #654

Closed
shazow opened this issue Dec 12, 2015 · 2 comments
Closed

Async work indicator #654

shazow opened this issue Dec 12, 2015 · 2 comments

Comments

@shazow
Copy link
Contributor

shazow commented Dec 12, 2015

The new neovim-enabled features are too fast!!

It's really hard to tell if anything is going on. Would be swell to have somekind of indicator to show that work is being done in the background.

Not sure how feasible it is to do this in a way that is compliant with everyone's layout settings, but maybe somekind of automagic integration with airline?

Also maybe this is better solved as a general job queue visualization rather than vim-go specific thing, worth debating.

(Related comment: #607 (comment))

@fatih
Copy link
Owner

fatih commented Dec 12, 2015

Hi @shazow

Unfortunately I don't know anything that can be added automatically. I'm not in favor of modifying the statusline ourselves btw. However there is a new function called go#jobcontrol#Statusline() which is exactly for this. It returns the current job status and is meant to be used as a notification. Right now there are no ways to notify a user in an async way. Please use this function with airline, lightline or just manually. I'm closing this as this is already implemented. Please let me know if this doesn't solve this issue or is not sufficient and I'm happy to open it again :)

@fatih fatih closed this as completed Dec 12, 2015
@shazow
Copy link
Contributor Author

shazow commented Dec 12, 2015

I think that's fair. :)

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

2 participants