All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Dave Blanchard <dave@killthe.net>, qemu-devel@nongnu.org
Subject: Re: Qemu resets terminal to crazy defaults
Date: Tue, 19 Dec 2023 16:38:56 -0300	[thread overview]
Message-ID: <87plz22d9r.fsf@suse.de> (raw)
In-Reply-To: <20231219132135.c4bff4807c9d7215b179f240@killthe.net>

Dave Blanchard <dave@killthe.net> writes:

> Hello all, can you please help me to understand what Qemu is doing here? 
>
> When connecting to the guest for example using a serial/tcp/telnet link, some kind of code is being immediately transmitted over the link which screws up my Xterm terminal settings, including changing the text cursor shape and most notably, disabling wraparound of long lines, so that they get truncated at the edge of the window instead. 
>
> Can this behavior be disabled by command line, and if not, what is the code doing exactly so I can know where to disable it? I tried disabling all calls to tcsetattr() but that had no effect.
>
> Dave

I looked into the automatic margins issue a long time ago and I seem to
remember it was caused by the firmware (SeaBIOS) configuring the
terminal and QEMU just never returning it to the original state. I
eventually gave up trying to fix it because I was having trouble finding
a reliable point in QEMU shutdown sequence to enable the capability
back. Nowadays I just run 'tput smam' after quitting QEMU.

Not a lot of help, I know. Hopefuly someone else has more information
about this. I'd be interested in finding a proper solution for this
situation.


  parent reply	other threads:[~2023-12-19 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 19:21 Qemu resets terminal to crazy defaults Dave Blanchard
2023-12-19 19:38 ` Warner Losh
2023-12-19 19:38 ` Fabiano Rosas [this message]
2023-12-19 20:53   ` Peter Maydell
2023-12-19 21:04     ` Warner Losh
2023-12-20 15:23       ` Fabiano Rosas
2023-12-20 15:33         ` Dave Blanchard
2023-12-20 16:57         ` BALATON Zoltan
2023-12-21 13:29           ` Fabiano Rosas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plz22d9r.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=dave@killthe.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.