From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Fix whitespace and indentation in lib/tuiterm.exp
Date: Thu, 18 May 2023 09:31:41 +0200 [thread overview]
Message-ID: <20230518073141.21524-1-tdevries@suse.de> (raw)
I noticed a trailing whitespace and some indentation errors in lib/tuiterm.exp.
Fix these.
Tested by re-running the TUI test-cases (gdb.tui/*.exp and gdb.python/tui*.exp)
on x86_64-linux.
---
gdb/testsuite/lib/tuiterm.exp | 96 +++++++++++++++++------------------
1 file changed, 48 insertions(+), 48 deletions(-)
diff --git a/gdb/testsuite/lib/tuiterm.exp b/gdb/testsuite/lib/tuiterm.exp
index 195f14666f4..64a883e89a3 100644
--- a/gdb/testsuite/lib/tuiterm.exp
+++ b/gdb/testsuite/lib/tuiterm.exp
@@ -552,52 +552,52 @@ namespace eval Term {
# https://vt100.net/docs/vt510-rm/SGR.html
proc _csi_m {args} {
_log_cur "Select Graphic Rendition ([join $args {, }])" {
- variable _attrs
-
- foreach item $args {
- switch -exact -- $item {
- "" - 0 {
- set _attrs(intensity) normal
- set _attrs(fg) default
- set _attrs(bg) default
- set _attrs(underline) 0
- set _attrs(reverse) 0
- }
- 1 {
- set _attrs(intensity) bold
- }
- 2 {
- set _attrs(intensity) dim
- }
- 4 {
- set _attrs(underline) 1
- }
- 7 {
- set _attrs(reverse) 1
- }
- 22 {
- set _attrs(intensity) normal
- }
- 24 {
- set _attrs(underline) 0
- }
- 27 {
- set _attrs(reverse) 1
- }
- 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 {
- set _attrs(fg) $item
- }
- 39 {
- set _attrs(fg) default
- }
- 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 {
- set _attrs(bg) $item
- }
- 49 {
- set _attrs(bg) default
- }
- }
- }
+ variable _attrs
+
+ foreach item $args {
+ switch -exact -- $item {
+ "" - 0 {
+ set _attrs(intensity) normal
+ set _attrs(fg) default
+ set _attrs(bg) default
+ set _attrs(underline) 0
+ set _attrs(reverse) 0
+ }
+ 1 {
+ set _attrs(intensity) bold
+ }
+ 2 {
+ set _attrs(intensity) dim
+ }
+ 4 {
+ set _attrs(underline) 1
+ }
+ 7 {
+ set _attrs(reverse) 1
+ }
+ 22 {
+ set _attrs(intensity) normal
+ }
+ 24 {
+ set _attrs(underline) 0
+ }
+ 27 {
+ set _attrs(reverse) 1
+ }
+ 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 {
+ set _attrs(fg) $item
+ }
+ 39 {
+ set _attrs(fg) default
+ }
+ 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 {
+ set _attrs(bg) $item
+ }
+ 49 {
+ set _attrs(bg) default
+ }
+ }
+ }
}
}
@@ -614,7 +614,7 @@ namespace eval Term {
variable _chars
set lattr [array get _attrs]
foreach char [split $str {}] {
- _log_cur " Inserted char '$char'" {
+ _log_cur " Inserted char '$char'" {
set _chars($_cur_col,$_cur_row) [list $char $lattr]
incr _cur_col
if {$_cur_col >= $_cols} {
@@ -739,7 +739,7 @@ namespace eval Term {
variable _cur_row
set fn "wait_for"
-
+
set prompt_wait_for "$gdb_prompt \$"
debug_tui_matching "$fn: regexp: '$wait_for'"
base-commit: 6a99f006ecadaf604258b583dec642de2d6f88ec
--
2.35.3
reply other threads:[~2023-05-18 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230518073141.21524-1-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).