Feature request: source venv on output split launch

[rileythai]

For development workflows, jukit could source the venv in the current working directory while opening an output split. This should be helpful for users who want to run quick checks, tests, or other actions in an iPython split.

I presume all that would have to be done is get it to find venv or .venv in the CWD and source it beforehand, but something really simple would be:

source .venv/bin/activate && ipython -i -c ...{REST OF COMMAND}

[arorashivoy]

you can do that using :JukitOut source .venv/bin/activate which would run the source .venv/bin/activate line first and then open the Jukit Output