public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] GDB/doc: Remove extraneous spaces from completion examples
Date: Fri, 01 Jul 2022 18:46:34 +0300	[thread overview]
Message-ID: <837d4wesyt.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2206302006560.10833@tpp.orcam.me.uk> (macro@embecosm.com)

> Date: Fri, 1 Jul 2022 16:13:05 +0100 (BST)
> From: "Maciej W. Rozycki" <macro@embecosm.com>
> (gdb) info bre<TAB>
> (gdb) info breakpoints
> 
> does the right thing, but is not what is shown in the manual.
> 
> In other cases an extraneous space is used that does not correspond to 
> the actual completion pattern shown, which gives an impression of 
> sloppiness.
> 
> Remove extraneous spaces then from completion examples as appropriate.
> ---
> Hi,
> 
>  Noticed while making documentation updates for "NUMBER" completion.
> 
>  OK to apply?

Yes, thanks.

  reply	other threads:[~2022-07-01 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 15:13 Maciej W. Rozycki
2022-07-01 15:46 ` Eli Zaretskii [this message]
2022-07-01 16:13   ` Maciej W. Rozycki

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=837d4wesyt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@embecosm.com \
    /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).