I use the SSH/Telnet client extensively and have noticed some usability issues and significant differences from v2023 with the new v2024 release:
Rich Harrington
Saint Xavier University Programmer Analyst Chicago
- Password displayed in SSH window in plain text. It used to be sent without echoing to the screen. Not significant but possibly an unintended change.
- UNABLE TO COPY / PASTE from right click menu in the SSH window. Actually no right click menu at all. Ctrl+C / Ctrl+V works but what was simple and intuitive – right-click copy from the editor and right-click paste to SSH – is now a two-hand operation.
- COPYING ONE LINE OF TEXT (Ctrl+C) AND PASTING (Ctrl+V) INTO SSH WINDOW POSTS THE COPIED TEXT INTO THE WINDOW TWICE. This problem coupled with the issue listed next – missing line terminations – causes the doubled command to throw an error.
- SOMETHING WEIRD IS HAPPENING WITH LINE TERMINATIONS. They are not being handled the same way they used to be – I don't know if the issue is that the SSH window is not honoring the UE/UES editor settings Conversions or DOS/Unix/Mac handling regarding how line terminations are handled between systems, but UE/UES SSH is not behaving the way it used to do. In the previous version I could copy a block of commands into the SSH window an each line-terminated command would be processed singly in sequence. With v2024 and possibly the line terminations missing from the command block – the server can't parse the block and naturally throws an error trying to process the big blob of undelimited text. If I can figure out if there is a combination that works with our server SSH I'll post back.
- THE SSH WINDOW IS NOT SENDING THE TAB CHARACTER. My primary use of UE/UES SSH is copying a command or block of commands from my text file repository of commands and pasting that into the SSH window, and then editing the results. Normally I will send a command that creates a create tab delimited .csv file on the server and copy/paste the results into Excel – however, the commands that I'm sending from v2024 specifying a tab delimited file WITH THE ASCII TAB CHARACTER actually contained in the script command text are being returned as SPACE delimited rather than TAB delimited. Even though the tab is in the command when it's pasted into the window, the command actually sent to the server does NOT specify the tab. I suspect this is related to the issue with line feeds.
Rich Harrington
Saint Xavier University Programmer Analyst Chicago