-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: use runtime alias strategy #2
Conversation
Obviously, this would have broader implications for the |
Looks good so far! Had the plan to implement the validity check before every Can you make sure to enable edit permissions to the PR once it's ready? Couldn't mark the previous PR as merged. |
I've unclutted
Thanks again for your contribution, I really appreciate it 🥳 |
The existing shell init strategy lends itself to frequent state errors as VSCode sessions start and stop. It also carries the limitation of having to restart the shell after you start the VSCode session.
Executing the
code_connect.py
script before every call tocode
ensures that the proper socket is detected without fail. The latency drawback is nearly imperceivable, clocking in between 30-60 ms.With this approach, we can do away with
activate.sh
andactivate.fish
... instead all we need is a simple alias like so