On Fri, Apr 27, 2018 at 05:23:36PM +, Thorsten Glaser wrote:
> From looking at the code, I donb t think it entirely correct.
> Thereb s a tty_hasstate, and one of the comments around it says
> /*
>* Only restore tty settings if job was originally
>* started in the
On Sat, Mar 31, 2018 at 09:36:23PM +, Thorsten Glaser wrote:
> Hi,
>
> I sometimes have weird tty state even after a process finished;
> this is mostly mpg123 running in foreground, so no backgrounding
> involved. When I then press Enter, the tty is back to normal
> state; is that true for
Hi again,
>Thinking a bit more about this, I found a valid reason not to keep the
>terminal state after a restarted job exits (successfully): the tty
>state in which that job was started can be obsolete at the time it is
>restarted because the tty state may have been modified while the job was
G.raud Meyer dixit:
>First one should know what is the correct behaviour. The feature of
[…]
>Before a patch fixing the strange case of a "successful but temporarily
>stopped job has failed" it would be good to document the feature (and
>the bug, if it is one).
I honestly don’t know.
It is
