Skip to content

Add support for Xonsh Shell #3487

Closed as not planned
Closed as not planned

Description

Add support for the Python based shell, Xonsh (https://xon.sh/)

Activity

  1. meatballs commented on Dec 19, 2018

    @meatballs
    Author

    This seems to have the 'needs PR' label but I've created #3488 for this issue. Is there something else I need to do?

  2. 8 remaining items

  3. anki-code commented on Sep 10, 2020

    @anki-code

    Thanks! We're really waiting the xonsh support.

  4. curtisma commented on Dec 5, 2021

    @curtisma

    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.

    Don Jayamanne (@DonJayamanne) Anthony Scopatz (@scopatz)

  5. anki-code commented on Dec 5, 2021

    @anki-code

    Hi Curtis Mayberry (@curtisma)! Try this - https://github.com/jnoortheen/vscode-xonsh - Adds xonsh language support for VSCode Editor.

  6. brettcannon commented on Dec 6, 2021

    @brettcannon
    Member

    There are currently no plans and due to the number of upvotes it is unfortunately not a top priority for us.

  7. curtisma commented on Dec 7, 2021

    @curtisma

    There are currently no plans and due to the number of upvotes it is unfortunately not a top priority for us.

    Ok, makes sense.

  8. jd-solanki commented on May 20, 2022

    @jd-solanki

    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?

  9. brettcannon commented on May 20, 2022

    @brettcannon
    Member

    JD Solanki (@jd-solanki) none that I'm aware of. How does xonsh activate a virtual environment mormally?

  10. jd-solanki commented on May 23, 2022

    @jd-solanki

    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:

    Screencast.from.23-05-22.10_19_33.AM.IST.mp4

    (It automatically activates the virtual env when I open the terminal)

    Whereas when I use xonsh with the same vscode env:

    Screencast.from.23-05-22.12_00_07.PM.IST.mp4

    No interpreter is selected 😢

  11. brettcannon commented on Dec 18, 2023

    @brettcannon
    Member

    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).

  12. locked as resolved and limited conversation to collaborators on Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions