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

Don't whine when intero was manually killed #96

Open
parsonsmatt opened this issue Sep 14, 2017 · 2 comments
Open

Don't whine when intero was manually killed #96

parsonsmatt opened this issue Sep 14, 2017 · 2 comments

Comments

@parsonsmatt
Copy link
Owner

Sometimes I kill the Intero process in order to save memory usage. When I do so, every time I save with the Neomake maker I get an error that the Intero process is still starting up.

@kokobd
Copy link

kokobd commented Nov 3, 2017

Same issue after I quit vim accidentally. Intero no longer works for the current project even if I re-install it. It works for my other projects though.

@parsonsmatt
Copy link
Owner Author

To do this, it seems like we should save a flag that indicates (to the best of our knowledge) whether or not intero is "on." This state would be updated on start/stop of the intero process, and we could update it if we get any errors (eg if I kill intero manually, then try to get the type of something, it should say "Intero isn't active" and then save that information).

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

2 participants