aboutsummaryrefslogtreecommitdiff
path: root/gdb/tui
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2021-12-24 22:31:53 -0700
committerTom Tromey <tom@tromey.com>2022-01-05 11:36:33 -0700
commitb58f47ab4cae11166f210f54bca6e7c58b855a0f (patch)
tree71a3a29e7574066997f1e5c6ef4df785ad928f98 /gdb/tui
parentb68178b9cbbef2aa4e234db4313ac8ba6d1dc04c (diff)
downloadgdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.zip
gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.gz
gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.bz2
Use filtered output in ordinary commands
Many otherwise ordinary commands choose to use unfiltered output rather than filtered. I don't think there's any reason for this, so this changes many such commands to use filtered output instead. Note that complete_command is not touched due to a comment there explaining why unfiltered output is believed to be used.
Diffstat (limited to 'gdb/tui')
-rw-r--r--gdb/tui/tui-regs.c12
1 files changed, 6 insertions, 6 deletions
diff --git a/gdb/tui/tui-regs.c b/gdb/tui/tui-regs.c
index a4eda65..16b6c08 100644
--- a/gdb/tui/tui-regs.c
+++ b/gdb/tui/tui-regs.c
@@ -606,20 +606,20 @@ tui_reg_command (const char *args, int from_tty)
struct reggroup *group;
int first;
- printf_unfiltered (_("\"tui reg\" must be followed by the name of "
- "either a register group,\nor one of 'next' "
- "or 'prev'. Known register groups are:\n"));
+ printf_filtered (_("\"tui reg\" must be followed by the name of "
+ "either a register group,\nor one of 'next' "
+ "or 'prev'. Known register groups are:\n"));
for (first = 1, group = reggroup_next (gdbarch, NULL);
group != NULL;
first = 0, group = reggroup_next (gdbarch, group))
{
if (!first)
- printf_unfiltered (", ");
- printf_unfiltered ("%s", reggroup_name (group));
+ printf_filtered (", ");
+ printf_filtered ("%s", reggroup_name (group));
}
- printf_unfiltered ("\n");
+ printf_filtered ("\n");
}
}