From: Eli Zaretskii <eliz@gnu.org>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH:doc] GDB/MI attribute names
Date: Sat, 26 Sep 2009 09:00:00 -0000 [thread overview]
Message-ID: <83bpkyt6z6.fsf@gnu.org> (raw)
In-Reply-To: <19133.17613.991722.489023@totara.tehura.co.nz>
> Date: Sat, 26 Sep 2009 10:31:41 +1200
> Cc: gdb-patches@sources.redhat.com
> From: nickrob@snap.net.nz (Nick Roberts)
>
> I can guess what it means but why are there three pairs of double
> quotes? When inserted into info it all gets enclosed in further
> single quotes. The usual meaning of `string' gets re-defined and *
> means 0 or more, so the empty string would be valid. Also we
> probably don't want a field name to start with a digit. Current
> names don't use digits at all and my initial proposal was not to
> include them in the specification.
If Texinfo markup and the way the result looks in Info are the
problem, then tell me how would you like it to look in Info, and I
will suggest the markup.
Wrt rest, I will go with anything you two agree upon. I only tried to
suggest alternatives from the documentation readability POV, not
because I know more about the subject matter than you do. IOW, my
comments were stylistic, not about the essence.
next prev parent reply other threads:[~2009-09-26 9:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:04 Nick Roberts
2009-09-25 8:09 ` Eli Zaretskii
2009-09-25 10:55 ` Nick Roberts
2009-09-25 11:09 ` Vladimir Prus
2009-09-25 12:34 ` Nick Roberts
2009-09-25 12:53 ` Vladimir Prus
2009-09-25 13:19 ` Eli Zaretskii
2009-09-25 13:35 ` Vladimir Prus
2009-09-25 13:59 ` Eli Zaretskii
2009-09-25 14:15 ` Vladimir Prus
2009-09-25 15:54 ` Eli Zaretskii
2009-09-25 22:32 ` Nick Roberts
2009-09-25 23:12 ` Nick Roberts
2009-09-28 16:25 ` Vladimir Prus
2009-09-26 9:00 ` Eli Zaretskii [this message]
2009-09-25 13:13 ` Eli Zaretskii
2009-09-25 13:40 ` Vladimir Prus
2009-09-25 13:07 ` Eli Zaretskii
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=83bpkyt6z6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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