qm terminal artifacts and glitches

kamzata

Renowned Member
Jan 21, 2011
235
9
83
Italy
Whenever I connect using qm terminal I bump into some Terminal strange behaviors:

E.g.
  • Terminal window is not used anymore in its entirety (usually just a portion as in the video below)
  • Artifacts appear and soon the terminal become unusable
Those issues are present using different terminals (Alacritty, iTerm, Gnome Terminal, and so on...)

qm-terminal-issue.gif

Do you know a way in order to fix those?
 
  • Terminal window is not used anymore in its entirety (usually just a portion as in the video below)
that's kinda expected since the connection with `qm terminal` is only via serial interface, which has no way of exchanging information about the terminal size (in contrast to a local terminal)
you can show the size with
Code:
stty size
and set it with
Code:
stty cols <columns> rows <rows>

also i did not see any artifacts, what do you mean by that?

usually I would use ssh instead of qm terminal to connect to the virtual machine, that makes life much easier
 
How can I set those values dynamically and automatically?

In the video there're any artifacts showing but sometimes parts of command text persists in the screen. Using clear command helps to mitigate the situation for just a while. Then the only thing I can do is just closing the terminal application and reopen it.
 
How can I set those values dynamically and automatically?
you can't AFAIK, the client terminal program can't tell the terminal environment in the vm it's size since it's over a serial connection (even if it's just virtual) and this has no mechanism to do so

as i said, it's much more ergonomic to just use ssh to connect to the vm instead

In the video there're any artifacts showing but sometimes parts of command text persists in the screen. Using clear command helps to mitigate the situation for just a while. Then the only thing I can do is just closing the terminal application and reopen it.
it's possible that the TERMINAL environment variable is not set correctly (again something that can be detected and set automatically for local shell/terminal applications but not over serial) but for that i'd have to have a better description of those artifacts and the circumstances (or a video/screenshot)