This makes desk unusable in some pipelines (or any pipelines if you don't like guessing).
This is a little complicated to reproduce. For instance, changing the first command from ls to seq 10 usually succeeds. I'm not sure what the reason is here, but it is likely related to the fact that seq can produce output sooner than ls.
:; desk run hello ls | desk run hello tac
[hangs]^C
[1]+ Stopped desk run hello ls | desk run hello tac
:; fg
desk run hello ls | desk run hello tac
[exits]
Or, if run with no controlling tty, we get warnings but the pipeline is otherwise functional.
:; desk run hello ls | desk run hello tac
bash: cannot set terminal process group (6214): Inappropriate ioctl for device
bash: no job control in this shell
bash: cannot set terminal process group (6211): Inappropriate ioctl for device
bash: no job control in this shell
[correct output follows]
I think this all has something to do with multiple shells trying to manage the foreground process on the terminal. This can be avoided if desk run stops using the -i flag and simply injects . $DESK_ENV; in front of the command to run.
This makes desk unusable in some pipelines (or any pipelines if you don't like guessing).
This is a little complicated to reproduce. For instance, changing the first command from
lstoseq 10usually succeeds. I'm not sure what the reason is here, but it is likely related to the fact thatseqcan produce output sooner thanls.Or, if run with no controlling tty, we get warnings but the pipeline is otherwise functional.
I think this all has something to do with multiple shells trying to manage the foreground process on the terminal. This can be avoided if
desk runstops using the-iflag and simply injects. $DESK_ENV;in front of the command to run.