Kamil's answer worked well for me, but it turns out I had some minor additional requirements that I didn't realize until I saw the answer. How can I make this properly transparent? However, PS1 does not get set, the prompt is therefore not modified, and the deactivate command does not become available as it normally would. In my testing, the window stays open and is usable the pwd is set properly and the VIRTUALENV and PATH environment variables are properly modified by the script. It's good enough that I could live with it if I really had to, but I'm really bothered by the shortcomings.
The specific use case is that I want to open a window, start in a particular directory (in my case, a folder on the desktop which holds subdirectories for Python projects I'm working on), and have a Python virtual environment activated (in my case, a common "scratch" venv named SANDBOX located directly in that directory).Īfter much research, I eventually ended up with: #!/bin/bash (This is why I have a question to ask here.) The commands that have run impact the state of the shell.(This means that anything based on read, xterm -keep etc. After the commands run, the window stays open indefinitely, usable to input more shell commands.(Per documentation, this one must be sourced from Bash.) This causes a terminal window to open, and some commands to run, including another script.(This is intended to select an optional, alternate way of starting up a terminal window so I can not simply edit a. I can double-click an icon on my desktop.I am not especially tied to using a shell script for this purpose, but my requirements are as follows:
0 kommentar(er)
