As a user, I'd like my terminal to be left in a good state when an SSH connection breaks #15

Closed
opened 2019-05-14 19:59:16 +00:00 by sloum · 1 comment
Owner

We have a defer for any exit that sbould return the terminal to a correct state. Even a panic should still resolve this defer. However, if there is a broken SSH pipe there is no more code that can be executed since it was running on a remote machine that is no longer available. I am not sure if there is a solution to this, but it is something to think on.

In particular it will often leave the terminal in a non-echo, cbreak, alt screen buffer state. All of this can be easily resolved, but is confusing if someone doesnt know what to do to solve those issues.

We have a defer for any exit that sbould return the terminal to a correct state. Even a panic should still resolve this defer. However, if there is a broken SSH pipe there is no more code that can be executed since it was running on a remote machine that is no longer available. I am not sure if there is a solution to this, but it is something to think on. In particular it will often leave the terminal in a non-echo, cbreak, alt screen buffer state. All of this can be easily resolved, but is confusing if someone doesnt know what to do to solve those issues.
sloum added the
bug
label 2019-05-14 19:59:16 +00:00
sloum changed title from SSH Broken pipe leaves terminal in bad state to As a user, I'd like my terminal to be left in a good state when an SSH connection breaks 2019-05-14 20:07:52 +00:00
sloum added the
wontfix
label 2020-03-17 19:58:02 +00:00
Author
Owner

It does not seem that there is really a solution to this. It happens sometimes.

If a user regularly experiences this and finds this issue and does not know how to solve the problem: typing reset and then enter in most terminals should return you to your regular settings.

It does not seem that there is really a solution to this. It happens sometimes. If a user regularly experiences this and finds this issue and does not know how to solve the problem: typing `reset` and then enter in most terminals should return you to your regular settings.
sloum closed this issue 2020-03-17 19:59:37 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sloum/bombadillo#15
No description provided.