Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Blandy <jimb@red-bean.com>, gdb@sources.redhat.com
Subject: Re: Formatting of packet descriptions in GDB manual
Date: Sun, 13 Nov 2005 17:12:00 -0000	[thread overview]
Message-ID: <20051113171247.GA1945@nevyn.them.org> (raw)
In-Reply-To: <u4q6h32bk.fsf@gnu.org>

On Sun, Nov 13, 2005 at 12:53:51AM +0200, Eli Zaretskii wrote:
> > >   @code{z}@code{3}@code{,}@var{addr}@code{,}@var{length}
> > >
> > > is it important to have `z', `3', and the comma typeset as 3 separate
> > > characters, or is it okay to see a single string `z3,'?  At the time I
> > > looked at this section, the answer was not clear to me.  You seem to
> > > indicate that it's okay to produce a single string here, but what do
> > > others think.

I don't think they need to be typeset separately.  In fact, I don't
want them to be.  You can't search for useful things in the info manual
this way - to use search (rather than index) to reach the particular
packet, you have to know where the quotes are and search for z'`3.
Yuck.

> Perhaps we should use blanks between those @var's, but explain in the
> text that there shouldn't be blanks in the real packet, and give an
> example to demonstrate that

100% agree.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-11-13 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12  0:25 Jim Blandy
2005-11-12  7:07 ` Eli Zaretskii
2005-11-12  8:47   ` Jim Blandy
2005-11-12 22:53     ` Eli Zaretskii
2005-11-12 23:07       ` Jim Blandy
2005-11-13 17:12       ` Daniel Jacobowitz [this message]
2005-11-13 22:10         ` Eli Zaretskii
2005-11-14  2:29           ` Daniel Jacobowitz
2005-11-14  4:29             ` Eli Zaretskii
2005-11-14 13:49               ` Daniel Jacobowitz
2005-11-16  5:47                 ` Jim Blandy
2005-11-16  6:54                   ` 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=20051113171247.GA1945@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@red-bean.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