client display and terminal issues after using telnet #79
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#79
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?
These are similar or the same issues as referenced in #36. Confirmed as still an issue in develop branch.
Telnet sessions can break the state of the terminal, resulting in weird behaviour in the client display:
Most of these issues can persist even after quitting the client.
client.go
has functionhandleTelnet()
which ends withc.Draw()
. I've done a quick test to try resetting and reinitialising to handle any possible terminal issues:Let me know what you think - is this the right approach? I can do some more work on this and raise a PR.
I was not familiar with
reset
as an option for tput (tput being one of those things that I discover more about as I need to, but seemingly never before). This approach seems good to me. If you are getting good results with this, it certainly can't be worse than leaving it in a bad state. I think this is a good call.Fixed in #80