You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
elinks(1) has a wried hehavior that blocks the controlling terminal from
being written by other background processes, while this may be intended to
maintain the readability the ELinks TUI, it usually causing problems due to
processes that trying to write to the terminal will be suspended by SIGTTOU;
to make the problem worse, user can't notice this immediately until exiting
elinks(1); after that the shell would indicates one or more background
processes being suspend, like '[1]+ Stopped ...' reported by bash(1).
It is very annoying for me because sometimes I would need to start a program
like ssh(1), to setup some port forwardings for use within elinks(1), in the
background, for example 'ssh ... -L 8000:... -N &'; it works on beginning,
but sometimes the background process may want to report a networking issue,
by printing an error message to stderr, then it being suspended, and the web
server forwarded by the background process becomes unresponsive, ELinks
stucks on 'Making connection' status until finally timed out... This
situation can only be recovered by exiting elinks(1), 'bg' that suspended
process and start elinks(1) again.
elinks(1) has a wried hehavior that blocks the controlling terminal from
being written by other background processes, while this may be intended to
maintain the readability the ELinks TUI, it usually causing problems due to
processes that trying to write to the terminal will be suspended by SIGTTOU;
to make the problem worse, user can't notice this immediately until exiting
elinks(1); after that the shell would indicates one or more background
processes being suspend, like '[1]+ Stopped ...' reported by bash(1).
It is very annoying for me because sometimes I would need to start a program
like ssh(1), to setup some port forwardings for use within elinks(1), in the
background, for example 'ssh ... -L 8000:... -N &'; it works on beginning,
but sometimes the background process may want to report a networking issue,
by printing an error message to stderr, then it being suspended, and the web
server forwarded by the background process becomes unresponsive, ELinks
stucks on 'Making connection' status until finally timed out... This
situation can only be recovered by exiting elinks(1), 'bg' that suspended
process and start elinks(1) again.
A Debian user suggested the following patch:
The text was updated successfully, but these errors were encountered: