Bug#381878: does something funky when called from a non-interactive shell

> Job control is now mandatory in POSIX... perhaps it should be enabled by > default? Er, yeah. /Support/ for job control is mandatory, and -m is a standard option. Sorry about that. ...still, it seems to be affecting things in an unintuitive way, and one that still doesn't occur. Note that using

Bug#381878: does something funky when called from a non-interactive shell

> $ dash -c 'dash; read arg' > dash$ exit > [1] + 683 suspended (tty input) dash -c 'dash; read arg' > $ kill %1 > [1] + 820 terminated dash -c 'dash; read arg' > $ This behavior looks like what happens when a non-foreground process tries to read from the terminal. Compare the result of '( re

Bug#381878: does something funky when called from a non-interactive shell

> # non-interactive shell > $ dash -c 'dash; read arg' > dash$ exit > [1] + 683 suspended (tty input) dash -c 'dash; read arg' > $ kill %1 > [1] + 820 terminated dash -c 'dash; read arg' > $ > > # interactive shell > $ dash -i -c 'dash; read arg' > dash$ exit > read this! > $ adding the '-m'

Bug#381878: does something funky when called from a non-interactive shell

Package: dash Version: 0.5.3-3 Severity: normal Please compare: # non-interactive shell $ dash -c 'dash; read arg' dash$ exit [1] + 683 suspended (tty input) dash -c 'dash; read arg' $ kill %1 [1] + 820 terminated dash -c 'dash; read arg' $ # interactive shell $ dash -i -c 'dash; read arg' d