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

Find a better way to keep haxe server running when closing/opening windows #59

Open
kevinresol opened this issue Apr 25, 2016 · 4 comments

Comments

@kevinresol
Copy link
Contributor

As titled, atom-haxe tries to start haxe --wait for each atom window which results in Error: Couldn't wait on 127.0.0.1:6112 (can be seen when toggled completion debug log), if there is already a haxe server started by another atom window.

This is not a big deal, because the completion still works. It is just wasting a little CPU.

@jeremyfa
Copy link
Member

Yes, that's actually a temporary workaround to prevent the server from not being restarted when working with multiple windows and closing the one that has started the server.

Without this workaround, you could kill the server without knowing it when closing the window (and wonder why completion does not work anymore).

That said we should for sure look for a better way of handling this.

@jeremyfa jeremyfa changed the title Tries to start haxe --wait for each atom window Find a better way to keep haxe server running when closing/opening windows Apr 25, 2016
@kevinresol
Copy link
Contributor Author

arghhh, I see. That make sense.

@kevinresol
Copy link
Contributor Author

Just a small suggestion, what if check only when a completion is needed?

@jeremyfa
Copy link
Member

Yes, that could be an option. Will have to see that after the haxe rewrite is done.

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