aboutsummaryrefslogtreecommitdiff
path: root/gdb/value.c
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/value.c
parentb68178b9cbbef2aa4e234db4313ac8ba6d1dc04c (diff)
downloadbinutils-b58f47ab4cae11166f210f54bca6e7c58b855a0f.zip
binutils-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.gz
binutils-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/value.c')
-rw-r--r--gdb/value.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/gdb/value.c b/gdb/value.c
index 9c396db..37c949f 100644
--- a/gdb/value.c
+++ b/gdb/value.c
@@ -2649,11 +2649,11 @@ show_convenience (const char *ignore, int from_tty)
The user can't create them except via Python, and if Python support
is installed this message will never be printed ($_streq will
exist). */
- printf_unfiltered (_("No debugger convenience variables now defined.\n"
- "Convenience variables have "
- "names starting with \"$\";\n"
- "use \"set\" as in \"set "
- "$foo = 5\" to define them.\n"));
+ printf_filtered (_("No debugger convenience variables now defined.\n"
+ "Convenience variables have "
+ "names starting with \"$\";\n"
+ "use \"set\" as in \"set "
+ "$foo = 5\" to define them.\n"));
}
}