I would like to be able to start a konsole with 6 (for example) tabs open, and each one in a certain directory and having started a subshell and sourced a file full of environment variables (for working on virtualenvs - I put the shells in subshells, so I can erase the definitions by exiting the subshell). I saw that you can specify a directory for the shells to open in, and specify a command to run in each new shell, but I was unable to keep the sub-shell that had sourced the definitions. Maybe it ran, but it had definitly exited by the time I could use the shell. And I don't know how to make the konsole start with 6 tabs open. Also, if we could specify a set of (say) 6 tabs, each with a different working directory, that would be even better. Then I could open the konsole and be ready to work, with shells open on the code directory, the virtualenv directory, maybe one on the log directory, and virtualenvs activated already. In addition or as part of this implementation, maybe we could pick a "tab-profile" for each newly opened tab? There could be a default, but we could choose to open a tab with a different profile. This may require that tabs can also have their own profiles separate from the whole konsole window. Reproducible: Always
Some background on "virtualenv", in case you haven't seen it before. It is a way to compartmentalize your python environment - it changes your PATH and PYTHONPATH and adds another env variable or two. I source the "activation" file that does that in a subshell. So when I exit the subshell, all those definitions go away. Other people use virtualenvwrapper, which provides utilities that allow you to switch between virtualenvs. I think they just redefine your PATH and env variables. My request is to allow someone to do what I want ... run a subshell, source a file in that subshell, and leave it running for me to work in.
This is possible w/ --tabs-from-file and dbus commands. Let us know if that doesn't work for you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!