Closed meatballs closed 9 months ago
This seems to have the 'needs PR' label but I've created #3488 for this issue. Is there something else I need to do?
We are going through old issues and we noticed that no one from the team had replied to this issue. I want to apologize for the oversight and to let you know that the issue was reviewed by the team and triaged (as shown by the labels applied to this issue).
Thanks! We're really waiting the xonsh support.
I notice #3488 was closed due to inactivity, any plans to still include support for a Xonsh shell integrated into VS code? It looks like it was really close and would be a wonderful addition.
@DonJayamanne @scopatz
Hi @curtisma! Try this - https://github.com/jnoortheen/vscode-xonsh - Adds xonsh language support for VSCode Editor.
There are currently no plans and due to the number of upvotes it is unfortunately not a top priority for us.
There are currently no plans and due to the number of upvotes it is unfortunately not a top priority for us.
Ok, makes sense.
For me when my default shell is xonsh and I want to activate the virtual env when I open terminal from vscode it doesn't automatically activate the virtual env like it was doing for bash.
Is there any workaround for now?
@jd-solanki none that I'm aware of. How does xonsh activate a virtual environment mormally?
Hi, Below is a screen recording of when I use bash & in vscode the python extension is enabled and I have the default interpreter configured:
(It automatically activates the virtual env when I open the terminal)
Whereas when I use xonsh with the same vscode env:
No interpreter is selected 😢
After talking this over w/ the team, we are unfortunately closing this issue due to limited resourcing compared to the interest in this feature (about 4 👍/year).
Add support for the Python based shell, Xonsh (https://xon.sh/)