From b58f47ab4cae11166f210f54bca6e7c58b855a0f Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Fri, 24 Dec 2021 22:31:53 -0700 Subject: 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. --- gdb/tui/tui-regs.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'gdb/tui/tui-regs.c') 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"); } } -- cgit v1.1