Skip to content

Adding support for virtualfish, virtualenv for fish shell. #1071

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

Closed
tsalinger opened this issue Mar 14, 2018 · 2 comments
Closed

Adding support for virtualfish, virtualenv for fish shell. #1071

tsalinger opened this issue Mar 14, 2018 · 2 comments
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@tsalinger
Copy link

This issue has been moved from Microsoft/vscode/
Original author is
@anhdle14
@anhdle14


Version 1.22.0-insider
Commit 3817c89
Date 2018-03-09T13:53:26.466Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
OS Linux 4.15.6-300.fc27.x86_64 #1 SMP Mon Feb 26 18:43:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:

  1. Prepared virtualfish, fishshell. docs
  2. Changed the user setting:
    "python.venvPath": "$VIRTUALFISH_HOME",
    "python.envFile": "$VIRTUAL_ENV"
  1. Select Python Interpreter.
  2. Except base path: /usr/bin/python3/ and /usr/bin/python could not find virtualfish list envs.

This is more than a future request than actual issues.

Does this issue occur when all extensions are disabled?: Yes


@DonJayamanne
Copy link

@anhdle14
If you would like to use environment variables in the settings, then please check the documentation

You'll need to change it as follows:

    "python.venvPath": "${env:VIRTUALFISH_HOME}",
    "python.envFile": "${env:VIRTUAL_ENV}"

Please let me know how this goes.

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster feature-interpreter labels Mar 15, 2018
@anhdle14
Copy link

That would do the tricks, thank you for letting me know this. Sorry for the late reply though.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants