From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 2/3] [gdb/testsuite] Add invisible and blinking attributes in tuiterm
Date: Fri, 26 May 2023 15:02:59 +0200 [thread overview]
Message-ID: <20230526130300.20974-2-tdevries@suse.de> (raw)
In-Reply-To: <20230526130300.20974-1-tdevries@suse.de>
I noticed curses using the invisible and blinking attributes.
Add these in tuiterm.
Tested on x86_64-linux.
---
gdb/testsuite/gdb.tui/tuiterm.exp | 8 ++++++++
gdb/testsuite/lib/tuiterm.exp | 14 ++++++++++++++
2 files changed, 22 insertions(+)
diff --git a/gdb/testsuite/gdb.tui/tuiterm.exp b/gdb/testsuite/gdb.tui/tuiterm.exp
index ff0a3ac48ad..bccb7ef445a 100644
--- a/gdb/testsuite/gdb.tui/tuiterm.exp
+++ b/gdb/testsuite/gdb.tui/tuiterm.exp
@@ -691,6 +691,14 @@ proc test_attrs {} {
2 dim
22 normal
}
+ invisible {
+ 8 1
+ 28 0
+ }
+ blinking {
+ 5 1
+ 25 0
+ }
} {
setup_terminal 8 1
set re ""
diff --git a/gdb/testsuite/lib/tuiterm.exp b/gdb/testsuite/lib/tuiterm.exp
index 49ce79558c6..90b885d7ab4 100644
--- a/gdb/testsuite/lib/tuiterm.exp
+++ b/gdb/testsuite/lib/tuiterm.exp
@@ -556,6 +556,8 @@ namespace eval Term {
bg default
underline 0
reverse 0
+ invisible 0
+ blinking 0
}
}
@@ -580,18 +582,30 @@ namespace eval Term {
4 {
set _attrs(underline) 1
}
+ 5 {
+ set _attrs(blinking) 1
+ }
7 {
set _attrs(reverse) 1
}
+ 8 {
+ set _attrs(invisible) 1
+ }
22 {
set _attrs(intensity) normal
}
24 {
set _attrs(underline) 0
}
+ 25 {
+ set _attrs(blinking) 0
+ }
27 {
set _attrs(reverse) 0
}
+ 28 {
+ set _attrs(invisible) 0
+ }
30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 {
set _attrs(fg) $item
}
--
2.35.3
next prev parent reply other threads:[~2023-05-26 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 13:02 [pushed 1/3] [gdb/testsuite] Fix reverse attribute " Tom de Vries
2023-05-26 13:02 ` Tom de Vries [this message]
2023-05-26 13:03 ` [pushed 3/3] [gdb/testsuite] Add test-case gdb.tui/color-prompt.exp Tom de Vries
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=20230526130300.20974-2-tdevries@suse.de \
--to=tdevries@suse.de \
--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).