Beginners • Re: Opening a terminal window at startup and getting it to run in a virtual environment?

Thanks, my understanding is that the exec bash at the end keeps the terminal window open after the commands have been run.

Regarding the CORE - it IS a folder on my Desktop, and the path is correct (or else nothing else would run - and everything runs perfectly - except when I try to run it in the same window I've opened with my wayfire.ini file.)

Since I posted, I've modified things a bit and made *SOME* progress. I have modified the wayfire.ini code after the autostart line as follows:
And the code in my start.sh file is:
This DOES successfully open a terminal window on startup AND the window is running the virtual environment! However - any subsequent commands to run my python script fail, such as:
In the above example, and others, it always fails for being unable to find piper - which is the error it gives if I attempt to run my python code from outside of the CORE virtual environment. However - in this same window, after it fails for not finding piper, if I manually enter the python string to run my code - it works just fine. It's almost like, even though it's activating the environment in the window, the subsequent command to run the python script is being run from a non-virtual environment. I have also tried giving the explicit path to python in my virtual environment instead of just passing "python" - but I get the same results. Thoughts?

Statistics: Posted by dave xanatos — Mon Feb 17, 2025 12:57 am

---