From: "andrzej zaborowski" <balrogg@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Duplicate initializer in curses_keys.h
Date: Mon, 27 Oct 2008 20:44:26 +0100 [thread overview]
Message-ID: <fb249edb0810271244y308faeabn19ed267e9ebce2c5@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580810271239h76f85447yb0d365a72ea65f13@mail.gmail.com>
2008/10/27 Blue Swirl <blauwirbel@gmail.com>:
> Sparse complains about initializer entry defined twice in curses_keys.h:
> ['\t'] = 15, /* Tab */
> [0x009] = 23 | CNTRL, /* Control + i */
>
> Which one is correct?
Turns out both are correct :-p Ctrl + i and Tab are indistinguishable
in console. While it doesn't matter when the guest is also a unix
console, I guess Tab is more useful so I'll remove ^I.
Cheers
next prev parent reply other threads:[~2008-10-27 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 19:39 [Qemu-devel] Duplicate initializer in curses_keys.h Blue Swirl
2008-10-27 19:44 ` andrzej zaborowski [this message]
2008-10-27 19:45 ` Samuel Thibault
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=fb249edb0810271244y308faeabn19ed267e9ebce2c5@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=blauwirbel@gmail.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 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).