-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Semi-automatic activation #204
Comments
Hi @Evpok. Environments shouldn't be automatically activated via |
Hi @justinmayer, let me try to reformulate: I wish to have links between directories and environments without using automatic activation, which is currently not supported. The behaviour I am looking for is for |
So, to summarize, you want to save a few keystrokes by typing |
More like |
My suggestion would be to define an abbreviation, replacing abbr -a vfa vf activate (cat $VIRTUALFISH_ACTIVATION_FILE) That way you get what you want in three keystrokes. But if you want to submit a pull request that activates the relevant virtual environment when Thoughts? |
Right, I'll do both: start with the abbreviation and see if I can get a PR to work. Thanks! |
Feature Request
I really like the idea of linking directories to envs, but at the same time I don't always want to activate the linked env when I
cd
into a dir. It would be nice if there was way to manually activate the environment linked to byvf connect
even withauto_activation
disabled. This could take the form of a dedicated command, or just the behaviour ofvf activate
without specifying an env (look intoVIRTUALFISH_ACTIVATION_FILE
and activate the env you find there`.The text was updated successfully, but these errors were encountered: