public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Maciej W. Rozycki <macro@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] GDB/doc: Remove indentation from `print -elements' completion example
Date: Fri,  1 Jul 2022 16:12:45 +0000 (GMT)	[thread overview]
Message-ID: <20220701161245.42DE7385E001@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a89c17dac1e1b921188ba014cafc9c82e33dd5e8

commit a89c17dac1e1b921188ba014cafc9c82e33dd5e8
Author: Maciej W. Rozycki <macro@embecosm.com>
Date:   Fri Jul 1 17:11:09 2022 +0100

    GDB/doc: Remove indentation from `print -elements' completion example
    
    Remove indentation from the text of the manual after the example here:
    
    "  Completion will in some cases guide you with a suggestion of what
    kind of argument an option expects.  For example:
    
         (gdb) print -elements <TAB><TAB>
         NUMBER     unlimited
    
       Here, the option expects a number (e.g., '100'), not literal
    'NUMBER'.  Such metasyntactical arguments are always presented in
    uppercase."
    
    as this is a continuation of the same paragraph.

Diff:
---
 gdb/doc/gdb.texinfo | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index ad5bc7db01e..7a4e337d15b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -2176,6 +2176,7 @@ of argument an option expects.  For example:
 NUMBER     unlimited
 @end smallexample
 
+@noindent
 Here, the option expects a number (e.g., @code{100}), not literal
 @code{NUMBER}.  Such metasyntactical arguments are always presented in
 uppercase.


                 reply	other threads:[~2022-07-01 16:12 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=20220701161245.42DE7385E001@sourceware.org \
    --to=macro@sourceware.org \
    --cc=gdb-cvs@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).