-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement PowerShell profile #42
Comments
shellLauncher
setting depends on a particular PowerShell profile configuration
This issue will now track effort on the PowerShell profile implementation. Things like automatic activation of the virtual environment, populating |
Maybe I can minimally touch the user's profile by asking them to run |
These two are roughly equivalent: In the # If there is an `.env` file in the PWD, load environment variables from it
Set-PsEnv In #* Import dotenv aka .env environment variables if it is found
if [ -f ./.env ] ; then
set -o allexport # enable shell option to export all created variables
source ./.env # now this will export all vars instead of just one
set +o allexport # disable shell option to export all created variables
fi |
Even though we aren't bundling a PowerShell profile or |
PowerShell profile tinkering is automatically done in |
This is completed in |
My PowerShell profile activates virtual environments detected in the current environment. I could instruct first-time contributors to modify their profile in
CONTRIBUTING.md
, but it would be nice to ship the appropriate profile options.Maybe we can include a profile mix-in that can be dot-sourced by users.
The text was updated successfully, but these errors were encountered: