Is your feature request related to a problem? Please describe.
When you open an SSH or Telnet session, the terminal appears right away as if you were already connected, but the connection is still being made in the background. There is no message telling you it is connecting. If the connection or the login fails, the error is only shown after you have already typed one or more commands, and what you typed is lost. On devices with no keyboard this is worse, because typing a command takes time and effort before you find out the session never connected.
Describe the solution you'd like
Show a "Connecting..." message and do not accept commands until the session is ready. If the connection or the login fails, show the error right away, before any command can be typed. This applies to both SSH and Telnet, since they share the same session screen.
Describe alternatives you've considered
Leaving it as it is and letting the user find out by typing a command, but that wastes time and loses the typed input when the session fails.
Additional context
I have a small change ready for this. It shows the message with displayTextLine so it follows the active theme, and you can still cancel with the back button while it is connecting. Tested on a LilyGo T-Embed CC1101 Plus against a Linux host and a Windows 11 host.
Is your feature request related to a problem? Please describe.
When you open an SSH or Telnet session, the terminal appears right away as if you were already connected, but the connection is still being made in the background. There is no message telling you it is connecting. If the connection or the login fails, the error is only shown after you have already typed one or more commands, and what you typed is lost. On devices with no keyboard this is worse, because typing a command takes time and effort before you find out the session never connected.
Describe the solution you'd like
Show a "Connecting..." message and do not accept commands until the session is ready. If the connection or the login fails, show the error right away, before any command can be typed. This applies to both SSH and Telnet, since they share the same session screen.
Describe alternatives you've considered
Leaving it as it is and letting the user find out by typing a command, but that wastes time and loses the typed input when the session fails.
Additional context
I have a small change ready for this. It shows the message with displayTextLine so it follows the active theme, and you can still cancel with the back button while it is connecting. Tested on a LilyGo T-Embed CC1101 Plus against a Linux host and a Windows 11 host.