From: Andrew Burgess Date: Tue, 22 Apr 2025 16:32:53 +0000 (+0100) Subject: gdb/doc: use @samp{} in Python docs X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4183b1e3a2f36dd67e25dff4be642c48bf214d64;p=thirdparty%2Fbinutils-gdb.git gdb/doc: use @samp{} in Python docs In this review: https://inbox.sourceware.org/gdb-patches/86sem6ase5.fsf@gnu.org it was pointed out that I should use @samp{} around some text I was adding to the documentation. However, the offending snippet of documentation was something I copied from elsewhere in python.texi. This commit fixes the original to use @samp{}. --- diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index 50342bbba5f..80f4c143f9f 100644 --- a/gdb/doc/python.texi +++ b/gdb/doc/python.texi @@ -4554,8 +4554,8 @@ registered. The help text for the new command is taken from the Python documentation string for the command's class, if there is one. If no -documentation string is provided, the default value ``This command is -not documented.'' is used. +documentation string is provided, the default value @samp{This command +is not documented.} is used. @end defun @cindex don't repeat Python command