From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-23175-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 32339 invoked by alias); 13 Nov 2005 17:12:51 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 32331 invoked by uid 22791); 13 Nov 2005 17:12:49 -0000
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 13 Nov 2005 17:12:49 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54)
	id 1EbLPL-0000XC-63; Sun, 13 Nov 2005 12:12:47 -0500
Date: Sun, 13 Nov 2005 17:12:00 -0000
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
Message-ID: <20051113171247.GA1945@nevyn.them.org>
Mail-Followup-To: Eli Zaretskii <eliz@gnu.org>,
	Jim Blandy <jimb@red-bean.com>, gdb@sources.redhat.com
References: <8f2776cb0511111624h4d646cd9i1f86824c5edc613f@mail.gmail.com> <ubr0q2vl9.fsf@gnu.org> <8f2776cb0511120047y50b3a273pe17ddd5c53342be1@mail.gmail.com> <u4q6h32bk.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <u4q6h32bk.fsf@gnu.org>
User-Agent: Mutt/1.5.8i
X-SW-Source: 2005-11/txt/msg00245.txt.bz2

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