From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb@sourceware.org
Subject: Re: building gdb with TUI support on Windows
Date: Thu, 01 Jan 2015 15:42:00 -0000 [thread overview]
Message-ID: <83mw62bj93.fsf@gnu.org> (raw)
In-Reply-To: <752802600.3289238.1420115247923.JavaMail.yahoo@jws11165.mail.ir2.yahoo.com>
> Date: Thu, 1 Jan 2015 12:27:27 +0000 (UTC)
> From: Hannes Domani <ssbssa@yahoo.de>
>
> Eli Zaretskii <eliz@gnu.org> schrieb am 17:34 Mittwoch, 31.Dezember 2014:
> > > For special keys, getch() has to be called multiple times and it returns
> > > part of the an escape sequence each call (e.g. 0xe0 + 'K' for left arrow).
> > >
> > > When keypad is enabled, wgetch() returns a single integer (e.g. KEY_LEFT).
> > > When disabled, it should return the escape sequence as getch() does.
> >
> > Sorry, I'm missing something here. AFAIK, "gdb -tui" doesn't call
> > 'getch', it calls 'wgetch'. Are you saying that when keypad is
> > disabled, GDB (or readline) somehow _expect_ to see escape sequences?
> > If not, I don't see why would the curses library need to start sending
> > escape sequences in that mode, it could simply continue sending single
> > keys, as it does in the keypad mode. What am I missing?
>
> Isn't that the whole point of the keypad option?
> At least that's how I understood this documentation:
> http://linux.die.net/man/3/keypad
That's just a man page from ncurses (which was what I read to learn
about the function), and it doesn't in any way preclude the
possibility that wgetch still returns single keys, rather than the
full escape sequence.
Put another way, if after the call to 'keypad', wgetch still returns a
single value, "gdb -tui" should still work. The problem could only
happen if wgetch returns ERR or doesn't return anything.
Anyway, I asked on the ncurses list about this, let's see what they
reply.
next prev parent reply other threads:[~2015-01-01 15:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:13 Ofir Cohen
2014-12-26 8:04 ` Eli Zaretskii
2014-12-27 13:53 ` Ofir Cohen
[not found] ` <CAHOBVAdux2M9aRnkJh1hDm_9VCTD6kVzWkF2fjj84qy8UJuh7w@mail.gmail.com>
2014-12-27 14:13 ` Eli Zaretskii
2014-12-27 14:40 ` Hannes Domani
2014-12-27 18:32 ` Eli Zaretskii
2014-12-28 13:58 ` Hannes Domani
2014-12-28 16:41 ` Ofir Cohen
2014-12-28 17:09 ` Hannes Domani
2014-12-28 23:34 ` Ofir Cohen
2014-12-29 0:41 ` Hannes Domani
2014-12-29 15:28 ` Ofir Cohen
[not found] ` <946370725.2390231.1419869855237.JavaMail.yahoo@jws11110.mail.ir2.yahoo.com>
2014-12-29 16:20 ` Hannes Domani
2014-12-30 19:15 ` Hannes Domani
2014-12-30 20:10 ` Ofir Cohen
2014-12-30 20:39 ` Hannes Domani
2014-12-31 16:34 ` Eli Zaretskii
2015-01-01 12:28 ` Hannes Domani
2015-01-01 15:42 ` Eli Zaretskii [this message]
2014-12-31 21:12 ` Ofir Cohen
2015-01-01 14:26 ` Hannes Domani
2015-01-01 15:14 ` Ofir Cohen
2015-01-01 15:47 ` Eli Zaretskii
2015-01-01 16:33 ` Ofir Cohen
2015-01-01 16:42 ` Eli Zaretskii
2015-01-01 16:48 ` Joel Sherrill
2015-01-01 17:18 ` Eli Zaretskii
[not found] ` <CAHOBVAcF824319G6O_LfJBYAQP3M0-LbhAV_d=SrR6jM4=0k5w@mail.gmail.com>
[not found] ` <83d26ybcap.fsf@gnu.org>
2015-01-02 0:32 ` Ofir Cohen
2014-12-28 18:38 ` Sergio Durigan Junior
2014-12-29 2:43 ` Joel Brobecker
2014-12-29 3:15 ` Joel Sherrill
2014-12-29 3:21 ` Joel Brobecker
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=83mw62bj93.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ssbssa@yahoo.de \
/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