As a user, I'd like my terminal to be left in a good state when an SSH connection breaks #15
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#15
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
SSH Broken pipe leaves terminal in bad stateto As a user, I'd like my terminal to be left in a good state when an SSH connection breaksIt 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.