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

vim-Import-JS can update wrong buffer if import-js is slow #47

Open
entropitor opened this issue Nov 20, 2018 · 0 comments
Open

vim-Import-JS can update wrong buffer if import-js is slow #47

entropitor opened this issue Nov 20, 2018 · 0 comments

Comments

@entropitor
Copy link

entropitor commented Nov 20, 2018

When ImportJS is slow (e.g. I didn't have watchman installed when I created this issue and I had a large mono-repo with a lot of dependencies), vim-import-js can behave badly in 2 ways:

  1. It can update the buffer AFTER other changes have been made to it (somewhat acceptable, I can imagine it's harder to know if the buffer has updated)
  2. It can update another buffer if a user has moved to this offer buffer by the time the results from import-js come back (which is really weird)
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

1 participant