Closed ferdinandyb closed 2 months ago
Conencted to https://github.com/contour-terminal/contour/issues/1326 and https://github.com/contour-terminal/contour/issues/1327
Also, some of the ssh logs must be moved into debug flags, with only two left as info for the user:
🔑 Starting SSH session to host: bferdinandy@192.168.17.227:2222
🔑 Connected to 192.168.17.227:2222
Abstract
If you start contour with an ssh profile, and the server is unreachable contour only gives some feedback on STDOUT and exists, the application itself is not started. If you launch contour without being attached to a terminal, you only see that nothing is happening. It would be better if contour started up and printed the error message. It might even be better, if in case the ssh profile is NOT the default profile, that contour would instead try to load the default profile. Also, a setting would be nice that would limit the amount of output on a successful connection.
Motivation
The current STDOUT feedback is on an unsuccessful connection is:
You don't see this when starting from the GUI, say an i3 shortcut or a windows shortcut.
A successful connection on the other hand has a lot of mostly unnecessary information:
Specification