El dom, 27 jun 2021 a las 17:13, Laurent Bercot ()
escribió:
> It sounds like your previous foreground process group (i.e. the
> processes that launch your script) attempted to write to, or read from,
> the terminal while your editor was running. That is pretty weird.
> Replace -g with -f, see w
Isn't job control the task of commands such as `foreground` and
`background`?
No, it's not. "foreground" means that the script waits for the
process being spawned to exit before resuming; "background" means that
the parent and the child execute in parallel. This has nothing to do
with job contr
El dom, 27 jun 2021 a las 6:33, Laurent Bercot ()
escribió:
> execline was not designed to handle interactive scripts: you need
> some extra tooling in the presence of job control.
>
Isn't job control the task of commands such as `foreground` and
`background`?
Is your opinion that this modifie
On bash, the editor receives ^C and ignores the signal properly.
On execline, foreground receives ^C and closes the whole script,
maybe causing me to lose the work done so far.
execline was not designed to handle interactive scripts: you need
some extra tooling in the presence of job contro
