![]() ![]() There are developers which have to maintain code for products with a lifetime of 10 to 20 years who need a long-time support for old versions of Windows beyond the support time of Microsoft because of the entire development environment is not available at all for newest version of Windows. Yes, that would be possible, but that would mean the SSH/telnet feature becomes unavailable for users of UltraEdit still using Windows Vista (hopefully nobody), Windows 7, Windows 8, Windows 8.1 and older versions of Windows 10 which are the platforms on which the built-in SSH/telnet support of UltraEdit is most needed as there is none by the used version of Windows. Someone might think now that the developers of UltraEdit could use the new terminal framework also for SSH/telnet support in UltraEdit. There are also very interesting blogs from Microsoft developers like Windows Command-Line: Unicode and UTF-8 Output Text Buffer. Windows 10 and Windows 11 have built-in very good support for colored terminal modes as Microsoft has even added a new framework just for that, see the Microsoft documentation page Windows Console and Terminal Ecosystem Roadmap and the other pages in menu on left side. But I can't help to find the right settings because I don't use SSH/telnet in my daily work with UltraEdit and UEStudio and have no remote device with a program which outputs what the program outputs which is started by you on the remote device. I still think this is just a configuration issue as this is just a character encoding and character display issue. I updated several posts and added posts to some topics if the reported issue is documented also in a post of the user to user forums. I know that there are really many other issues solved as I received emails from IDM support during beta testing period to do verification on fixes of issues reported by me in the past by email. So it would be necessary to run a test with UltraEdit for Windows v2022.0.0.70 if this issue has been addressed and belongs to the many issues resolved item which is the last item in file changes.txt of installed version 2022.0.0.70. There is written nothing about this box drawing characters display issue in SSH/telnet window on the new features tour page or the latest changes page. Perhaps you can see a significant difference regarding to terminal type and try out setting the terminal type in SSH account settings of UltraEdit to the string used by the Windows Terminal.ĭid you ask support of UltraEdit per email for help on this issue on which most likely nobody else than you is interested in a solution?ĭid you request an enhancement of the SSH/telnet support of UltraEdit for Windows? I suggest to run after establishing the SSH connection with Windows Terminal the command printenv and do the same in UltraEdit SSH console after establishing the connection and compare the two output environment variables list. I cannot find any information in the Microsoft documentation of the Windows Terminal about the used terminal type. It looks like iptraf-ng adapts its output on the terminal type and uses for the UltraEdit terminal types always black and white output as it thinks, the ANSI escape sequences for colored output are not supported by the terminal emulation used by UltraEdit. UltraEdit uses indeed automatically vt100 on leaving the terminal type edit field blank. This option is used to specify the terminal type set on the remote server (an Environment variable). I have no access to a device with SSH and so my suggestions below are just general hints according to little information read by me on several web pages just now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |