Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-readline@gnu.org,  gdb-patches@sources.redhat.com
Subject: Re: PATCH: Use getche on Win32
Date: Tue, 10 May 2005 11:45:00 -0000	[thread overview]
Message-ID: <42804E09.9060508@codesourcery.com> (raw)
In-Reply-To: <01c55512$Blat.v2.4$85bf3480@zahav.net.il>

Eli Zaretskii wrote:
>>Date: Mon, 9 May 2005 13:15:50 -0700
>>From: Mark Mitchell <mark@codesourcery.com>
>>Cc: gdb-patches@sources.redhat.com
>>
>>Windows console semantics are different from UNIX.  If we just use
>>"read" to read what the user's typing, we end up blocking until a
>>newline is available, and even then there are some oddities.  The
>>easiest thing seems to be to use the special "getche" (short for "get
>>character with echo") routine which does the right thing.
>>
>>Reviews?
> 
> 
> What happens if you press one of the special keys, like Ctrl-C or the
> arrow keys or PageDown?  Does getche still DTRT?

Ctrl-C shows up as code 3, despite the fact that the documentation says 
that you can't read Ctrl-C.  The arrows and such are two-byte sequences; 
the first byte is 0xE0, while the second byte is a letter.  For example, 
left-arrow is 0xE0 0x50.  So, I'm not sure this entirely qualifies as 
"DTRT", but it's not totally broken either.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304


  reply	other threads:[~2005-05-10  6:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 20:42 Mark Mitchell
2005-05-10  6:01 ` Eli Zaretskii
2005-05-10 11:45   ` Mark Mitchell [this message]
2005-05-10 20:05     ` Eli Zaretskii
2005-05-10 20:26       ` Mark Mitchell
2005-05-10 20:31         ` Eli Zaretskii
2005-05-10 20:49           ` Daniel Jacobowitz
2005-05-10 21:41             ` Christopher Faylor
2005-05-11  6:55               ` Christopher Faylor
2005-05-11  7:13                 ` Eli Zaretskii
2005-05-11  7:17                   ` Mark Mitchell
2005-05-11  7:21                 ` MinGW build instructions (was: PATCH: Use getche on Win32) Eli Zaretskii
2005-05-11  7:29                   ` MinGW build instructions Mark Mitchell
2005-05-11  7:53                     ` Eli Zaretskii
2005-05-11 18:45                     ` Christopher Faylor
2005-05-11 19:05                       ` Eli Zaretskii
2005-05-11 19:58                         ` Christopher Faylor
2005-05-11 23:16                           ` Eli Zaretskii
2005-05-11  6:56             ` PATCH: Use getche on Win32 Mark Mitchell
2005-05-11 13:42               ` Eli Zaretskii
2005-05-13 11:42                 ` Mark Mitchell
2005-05-13 15:18                   ` Eli Zaretskii
2005-05-11  7:07             ` Eli Zaretskii

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=42804E09.9060508@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=bug-readline@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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