Am 18.04.19 um 13:02 schrieb Laszlo Ersek:
On 04/18/19 07:02, Joachim Durchholz wrote:
Am 17.04.19 um 20:27 schrieb Laszlo Ersek:
So, let's look at your original question again (which was not a problem
statement):
So you need an explicit problem statement to know that somebody might
have a pr
On 04/18/19 07:02, Joachim Durchholz wrote:
> Am 17.04.19 um 20:27 schrieb Laszlo Ersek:
>> So, let's look at your original question again (which was not a problem
>> statement):
>
> So you need an explicit problem statement to know that somebody might
> have a problem?
You're on a technical mail
Am 17.04.19 um 20:27 schrieb Laszlo Ersek:
So, let's look at your original question again (which was not a problem
statement):
So you need an explicit problem statement to know that somebody might
have a problem?
what's the reasoning behind "We need a terminal output" in curses.c?
The rea
Hi Joachim,
On 04/17/19 19:09, Joachim Durchholz wrote:
> Sorry, I'm done having to argue against(!) a person who's stonewalling
> me by wilfully ignoring differences ("doesn't work perfectly"
> interpreted as "does not work at all"), discounting
> just-for-testing-purpose workarounds as if they w
Sorry, I'm done having to argue against(!) a person who's stonewalling
me by wilfully ignoring differences ("doesn't work perfectly"
interpreted as "does not work at all"), discounting
just-for-testing-purpose workarounds as if they were actual proposed
solutions ("not a sane approach"), ignori
Hi,
> Then I don't understand why it just ran fine.
> I don't expect fullscreen output to work perfectly anyway;
If you don't expect the output to actually work,
then fine, feel free to comment out that check.
I don't consider that being a sane approach though.
> just enough so I can use qemu
Am 16.04.19 um 09:24 schrieb Gerd Hoffmann:
On Mon, Apr 15, 2019 at 03:10:09PM -0400, John Snow wrote:
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?
curses needs a terminal.
I commented out the check, and guess w
On 04/16/19 09:24, Gerd Hoffmann wrote:
> On Mon, Apr 15, 2019 at 03:10:09PM -0400, John Snow wrote:
>>
>>
>> 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?
>
> curses needs a terminal.
>
>>> I don't really se
On Mon, Apr 15, 2019 at 03:10:09PM -0400, John Snow wrote:
>
>
> 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?
curses needs a terminal.
> > I don't really see a scenario where it's problematic if qemu emits
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 does
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
11 matches
Mail list logo
