Interestingly enough, some "xterm" emulators do not implement the newer ones. The latter are the original xterm sequences (early 1990s), the former are modern xterm (late 1990s). Using the infocmp program, you can see what its terminal database has for those values, e.g., smcup=\E[?1049h, So it is reasonable to suppose that MobaXterm also has the infocmp program. I don't have MobaXterm at hand to check, but you can check this. So it sounds as if mosh is seeing a local terminal description where the smcup and rmcup terminfo capabilities do not tell the "xterm" to switch to/from the alternate screen. It is more complicated than that: vim is actually using the terminal database on the machine where you are running it, but mosh is having the final say over what escape sequences are sent to the terminal. When using ssh, that library is on the remote machine.In the case of the mosh program, that library is on your local machine.The setting for TERM tells the termcap/terminfo/curses library which terminal description to use. MobaXterm uses PuTTY, which does implement this feature from xterm. The behavior where the screen is cleared and only a short message remains sounds like a program that is switching between xterm's normal and alternative screens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |