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

GT for VS Code stops working after the connected workspace is closed #275

Open
1 of 3 tasks
fregante opened this issue Mar 21, 2023 · 0 comments
Open
1 of 3 tasks

Comments

@fregante
Copy link
Owner

fregante commented Mar 21, 2023

Extensions are run once per workspace, so if there are two workspaces open, GhostText will open the port in one and then fail in the other one.

If the first workspace is closed, the other one does not attempt to open the port again.

Tasks:

  • Add enable/disable server commands, so that the user can try to restart the server
  • Detect workspace closures and try to reopen the server
  • Potentially look into launching a persistent child process and orchestrate VS Code from there, bypassing this setup (this would involve additional message passing step, so it's a last resort)

This also causes:

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

1 participant