From: Anthony Liguori <anthony@codemonkey.ws>
To: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix curses update
Date: Mon, 03 May 2010 13:06:46 -0500 [thread overview]
Message-ID: <4BDF10B6.80709@codemonkey.ws> (raw)
In-Reply-To: <20100422140811.GA27272@chrom.inf.tu-dresden.de>
On 04/22/2010 09:08 AM, Bernhard Kauer wrote:
> Hi,
>
>
>> I believe this issue has come up before with a similar patch but
>>
> well i've submitted such a patch more than two years ago. Unfortunatelly
> it got never applied, so that I have to patch my Qemu on every update...
>
>
>
>> someone checked their ncurses and they didn't see the same issue.
>> I just checked and here mvwaddchnstr() does not expect a null-terminated
>> string either, but it skips the \0 characters.
>>
> This is not conforming to the Single UNIX Specification, which states
> that the string is shown "until a null chtype is encountered". See for
> example:
> http://www.opengroup.org/onlinepubs/007908775/xcurses/addchstr.html
>
>
>
>> So probably we should
>> replace them with spaces or something else, I wouldn't like to
>> replace a single library call with 80 calls, it's better to go through
>> the string and replace them, maybe in console_write_ch or somewhere
>> else.
>>
> That would be a one-liner. Should I send such a patch?
>
Yes.
Regards,
Anthony Liguori
> Thanks,
>
> Bernhard
>
>
>
>
next prev parent reply other threads:[~2010-05-03 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 9:38 [Qemu-devel] [PATCH] fix curses update Bernhard Kauer
2010-04-22 1:27 ` andrzej zaborowski
2010-04-22 14:08 ` Bernhard Kauer
2010-05-03 18:06 ` Anthony Liguori [this message]
2010-05-20 20:53 ` [Qemu-devel] [PATCH] fix curses update - v2 Bernhard Kauer
2010-05-21 12:02 ` andrzej zaborowski
2010-05-21 12:43 ` Bernhard Kauer
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=4BDF10B6.80709@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kauer@os.inf.tu-dresden.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).