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

neovim: invoke guru functions via async api #1678

Merged
merged 1 commit into from
Mar 3, 2018

Conversation

entombedvirus
Copy link
Contributor

Previously, enabling auto_same_ids and auto_type_info in neovim on large
go projects resulted in a noticeable UI pause while neovim was waiting
for the guru process to produce output. This was not a problem in Vim8
since vim-go already uses the job_start async api for Vim8.

This commit enables transparent use of neovim jobstart api to accomplish
the same async behavior in neovim. This commit also fixes a bug where
enabling auto_same_ids prevented :GoImplements from correctly popping up
the location list.

@codecov-io
Copy link

codecov-io commented Feb 19, 2018

Codecov Report

Merging #1678 into master will decrease coverage by 0.02%.
The diff coverage is 9.09%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1678      +/-   ##
==========================================
- Coverage   19.75%   19.73%   -0.03%     
==========================================
  Files          57       57              
  Lines        4738     4748      +10     
==========================================
+ Hits          936      937       +1     
- Misses       3802     3811       +9
Flag Coverage Δ
#nvim 15.08% <9.09%> (-0.02%) ⬇️
#vim74 17.29% <9.09%> (-0.02%) ⬇️
#vim80 18.66% <9.09%> (-0.02%) ⬇️
Impacted Files Coverage Δ
autoload/go/guru.vim 9.52% <9.09%> (+0.01%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eaef6f7...ba2a1e8. Read the comment docs.

@bhcleek bhcleek self-requested a review March 1, 2018 17:41
@bhcleek
Copy link
Collaborator

bhcleek commented Mar 2, 2018

Thank you for the contribution @entombedvirus. I'm working on resolving the conflicts and will test these changes this weekend.

Previously, enabling auto_same_ids and auto_type_info in neovim on large
go projects resulted in a noticeable UI pause while neovim was waiting
for the guru process to produce output. This was not a problem in Vim8
since vim-go already uses the job_start async api for Vim8.

This commit enables transparent use of neovim jobstart api to accomplish
the same async behavior in neovim. This commit also fixes a bug where
enabling auto_same_ids prevented :GoImplements from correctly popping up
the location list.
@bhcleek
Copy link
Collaborator

bhcleek commented Mar 2, 2018

@entombedvirus do you mind if I force push over your branch with the rebased changes?

@entombedvirus
Copy link
Contributor Author

👍 Go for it.

@bhcleek bhcleek force-pushed the rohith/async-guru-neovim branch from c91792e to ba2a1e8 Compare March 3, 2018 01:27
@bhcleek bhcleek merged commit 5bc8d9e into fatih:master Mar 3, 2018
@bhcleek
Copy link
Collaborator

bhcleek commented Mar 3, 2018

Thank you.

bhcleek added a commit that referenced this pull request Mar 3, 2018
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

Successfully merging this pull request may close these issues.

3 participants