You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great tool, I'm still a bit of a noob. I work in a server based environment and each job is a separate python virtual environment with associated Jupyter Lab sessions.
When you open a terminal (Great Feature) it drops you in the correct folder but not in the virtual environment. Would it be possible to active the virtual environment?
The text was updated successfully, but these errors were encountered:
In general, an environment could be a pip virtual environment, a conda virtual environment, or any number of other things. I think the difficulty here would be figuring out what the "correct" thing to do here.
Perhaps the thing to do is to provide a setting for code to execute at the start of a terminal session? Then you could have whatever logic you want in place?
@jasongrout - Thanks for responding. :) That's a very good point. What about a concept similar to the .bashrc, .bash_profile, .profile, autoexec.bat, etc. If the user drops a .jlt_profile file that the terminal would execute. The user would be able to define what happens as needed.
Great tool, I'm still a bit of a noob. I work in a server based environment and each job is a separate python virtual environment with associated Jupyter Lab sessions.
When you open a terminal (Great Feature) it drops you in the correct folder but not in the virtual environment. Would it be possible to active the virtual environment?
The text was updated successfully, but these errors were encountered: