kingToolbox / WindTerm

A professional cross-platform SSH/Sftp/Shell/Telnet/Serial terminal.
https://kingtoolbox.github.io
23k stars 1.78k forks source link

The target machine `vim` editor connected through the fortress machine is abnormal #1544

Open staugur opened 1 year ago

staugur commented 1 year ago

ERR Image:

I found the bug, using 2.4.1 and 2.6.0 it persists.

We use a commercial bastion machine to connect to the intranet server, but after the bastion machine is connected to the target server, random garbled characters will appear in the lower right corner of the editor when using vim, even if you exit the editor, it will be output on the screen.

Chinese 我发现了错误,使用2.4.1和2.6.0仍然存在。

我们使用商业堡垒机连接内网服务器,但是堡垒机连接到目标服务器后,使用vim时编辑器右下角出现随机乱码提示,即便退出编辑器,也会在屏幕输出。

Superyunkai commented 1 year ago

I found a bug also about vim, using 2.5.0 and prerelease it persists I also use a commerical machine to connect to the server, and enter a docker container, in which I use vim edit the config file.Item seems what ever I typed, I disply "ESC[?0c" or "ESC[?1c". it seems a specificed coding set, but still I can't found the reson. firstly, I thought it happened because terminil encode seting.So, I check it, use utf-8 both side. secondly, I try other container in that server, and everthing ok. I don't what might relation to this bug

ademarguerreiro commented 1 year ago

Same problem here, none of the solutions i tried worked, disabling mouse commands, changing bash_profile, chaging Windterm's term and term-256, changing for a mono font, it persist.

I noticed that happens with RHEL based OS's servers and with EN-US language, if the language is PT-PT or PT-BR for me i could edit with nano and NVIM. Maybe is related to how Windterm is parsing our keyboard layout or something like that, from my point of view changing server language is not a solution, unfortunately for now i'm using another terminal, i really want to use Windterm, but this problem is a breaking bug for me.

Screenshot below, Alma Linux server. Posted in #1745 and #232 issues, but i found #863 is the same issue. error-wind