From: Patrick Palka <patrick@parcs.ath.cx>
To: gdb-patches@sourceware.org
Cc: Patrick Palka <patrick@parcs.ath.cx>
Subject: [PATCH 2/3] TUI: Don't print KEY_RESIZE keys
Date: Thu, 08 Jan 2015 04:05:00 -0000 [thread overview]
Message-ID: <1420689885-31156-2-git-send-email-patrick@parcs.ath.cx> (raw)
In-Reply-To: <1420689885-31156-1-git-send-email-patrick@parcs.ath.cx>
wgetch() sometimes returns KEY_RESIZE when ncurses detects that the
terminal has been resized. This character then gets passed on to
readline which interprets it as a multibyte character. Instead of
passing on this character to readline, intercept it as a (no-op) control
character and pass '\0' to readline.
gdb/ChangeLog:
* tui/tui-command.c (tui_dispatch_ctrl_char): Ignore KEY_RESIZE
keys.
---
gdb/tui/tui-command.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/tui/tui-command.c b/gdb/tui/tui-command.c
index d1a5ddb..dfcf512 100644
--- a/gdb/tui/tui-command.c
+++ b/gdb/tui/tui-command.c
@@ -121,6 +121,7 @@ tui_dispatch_ctrl_char (unsigned int ch)
tui_scroll_right (win_info, 1);
break;
case '\f':
+ case KEY_RESIZE:
break;
default:
c = ch_copy;
--
2.2.1.212.gc5b9256
next prev parent reply other threads:[~2015-01-08 4:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 4:05 [PATCH 1/3] Remove superfluous function key_is_command_char() Patrick Palka
2015-01-08 4:05 ` [PATCH 3/3] Don't flush the prompt when resizing the terminal within TUI Patrick Palka
2015-01-08 11:39 ` Pedro Alves
2015-01-08 4:05 ` Patrick Palka [this message]
2015-01-08 11:29 ` [PATCH 2/3] TUI: Don't print KEY_RESIZE keys Pedro Alves
2015-01-08 12:32 ` Patrick Palka
2015-01-08 13:22 ` Pedro Alves
2015-01-08 13:38 ` Patrick Palka
2015-02-11 0:25 ` Patrick Palka
2015-02-16 22:42 ` Pedro Alves
2015-02-17 0:53 ` Patrick Palka
2015-02-17 10:23 ` Pedro Alves
2015-02-17 13:02 ` Patrick Palka
2015-02-17 13:24 ` Patrick Palka
2015-01-08 11:40 ` [PATCH 1/3] Remove superfluous function key_is_command_char() Pedro Alves
2015-01-08 13:34 ` Eli Zaretskii
2015-01-08 13:48 ` Patrick Palka
2015-01-08 14:58 ` 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=1420689885-31156-2-git-send-email-patrick@parcs.ath.cx \
--to=patrick@parcs.ath.cx \
--cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).