Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matt Rice <ratmice@gmail.com>
Cc: dje@google.com, gdb-patches@sourceware.org
Subject: Re: Rename "info definitions"?
Date: Thu, 29 Sep 2011 07:20:00 -0000	[thread overview]
Message-ID: <83wrcreryp.fsf@gnu.org> (raw)
In-Reply-To: <CACTLOFrcvxQdKhQD0sktcfDS07XxKOFVj9cK7yORmwKKVgQAOg@mail.gmail.com>

> Date: Wed, 28 Sep 2011 19:13:58 -0700
> From: Matt Rice <ratmice@gmail.com>
> Cc: gdb-patches@sourceware.org
> 
> +info macro [-all] [--] MACRO
> +  The info macro command has new options -all and --.

Please quote the options with `..'.  Also, please have 2 spaces after
the period.

>                                                        The first or printing
                                                                   ^^
"for", I guess.

> +  all definitions of a macro.  The second for explicitly specifying the end
> +  of arguments and the beginning of the macro name.

I would add "in case the macro name starts with a hyphen".

> +@item info macro @r{[}-a@r{|}-all@r{]} @r{[}--@r{]} @var{macro}

You don't need the @r{} markup here.  It is only needed in the @def*
lines, because those cause the rest of the line automatically typeset
as in @var{}, which produces a slanted typeface in print.  Since we
want the square brackets typeset in the normal Roman typeface, we
countermand the slanted face with @r{}.  But @item does not have that
effect, so @r{} is not needed.

OK with those changes.


  reply	other threads:[~2011-09-29  7:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 19:34 Doug Evans
2011-09-21 20:28 ` Matt Rice
2011-09-23 17:38   ` Doug Evans
2011-09-29  2:16     ` Matt Rice
2011-09-29  7:20       ` Eli Zaretskii [this message]
2011-09-29 10:55       ` Pedro Alves
2011-09-29 12:41         ` Matt Rice
2011-09-29 13:28           ` Pedro Alves
2011-09-29 13:37             ` Pedro Alves
2011-09-29 13:56               ` Matt Rice
2011-09-29 14:01                 ` Pedro Alves
2011-10-03 21:18       ` Matt Rice
2011-10-04 16:51         ` Tom Tromey
2011-10-05  0:31           ` Matt Rice
2011-10-14 20:23             ` Tom Tromey
2011-11-12 17:03               ` Matt Rice
2011-11-12 17:09                 ` Matt Rice

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=83wrcreryp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ratmice@gmail.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