On Thu, 14 Dec 2023, Mayuresh wrote:
However, the fact remains that, if I use mlterm on a NetBSD VM there is no
issue even on a large screen. The issue is only when using mlterm on
Linux. Might have something to do with the OS' libraries and differences
in their handling of the terminal.
Since this is on Linux, you could try strace(1) or ltrace(1):
strace -rT -o /tmp/mlterm.log mlterm ...
Then, look at the 1st and last fields for anomalies (disregarding things
like read(), select(), poll()--which usually take some time to complete).
-RVP
