All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Joachim Durchholz <jo@durchholz.org>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] curses.c: "We need a terminal output" ?
Date: Mon, 15 Apr 2019 15:10:09 -0400	[thread overview]
Message-ID: <dbd6541e-5013-d0bc-b23e-a8de4f4cd171@redhat.com> (raw)
In-Reply-To: <874f0f8e-780e-6600-e11b-b97f5b055cf8@durchholz.org>

<CC'ing curses maintainer>

On 4/13/19 5:02 AM, Joachim Durchholz wrote:
> Hi all,
> 
> what's the reasoning behind "We need a terminal output" in curses.c?
> 
> I don't really see a scenario where it's problematic if qemu emits
> escape sequences to a pipe.
> I have experienced one scenario where it is problematic: It doesn't work
> properly with pexpect and expectit (a Python and a Java library that do
> expect). I suspect they fail to use a pty, but then I see no harm in not
> doing so.
> I can see another scenario when this is problematic: Unit testing code
> that directly writes to the console. E.g. testing BIOS code, or testing
> operating systems when using the serial port is not an option.
> 
> Regards,
> Jo
> 

  reply	other threads:[~2019-04-15 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13  9:02 [Qemu-devel] curses.c: "We need a terminal output" ? Joachim Durchholz
2019-04-15 19:10 ` John Snow [this message]
2019-04-16  7:24   ` Gerd Hoffmann
2019-04-16 14:02     ` Laszlo Ersek
2019-04-16 18:04     ` Joachim Durchholz
2019-04-17  7:10       ` Gerd Hoffmann
2019-04-17 17:09         ` Joachim Durchholz
2019-04-17 18:27           ` Laszlo Ersek
2019-04-18  5:02             ` Joachim Durchholz
2019-04-18 11:02               ` Laszlo Ersek
2019-04-18 18:06                 ` Joachim Durchholz

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=dbd6541e-5013-d0bc-b23e-a8de4f4cd171@redhat.com \
    --to=jsnow@redhat.com \
    --cc=jo@durchholz.org \
    --cc=kraxel@redhat.com \
    --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.