Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Remote "qSupported" features probe
Date: Tue, 13 Jun 2006 19:16:00 -0000	[thread overview]
Message-ID: <20060613191654.GA16866@nevyn.them.org> (raw)
In-Reply-To: <uejxs51z7.fsf@gnu.org>

On Tue, Jun 13, 2006 at 09:45:16PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 13 Jun 2006 14:35:26 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > > Did you look at how this empty @item is typeset in the printed version
> > > of the manual?  I suspect it won't do what you want.  Perhaps saying
> > > "(@emph{empty})" explicitly will look better.
> > 
> > Hmm.  We already use a bare @item in several places, so I didn't think
> > to check.  It comes out as `' in the appropriate font; do you think
> > that's OK?
> 
> It's not bad, but the following might be better:
> 
>   @item  @r{(empty)}

That seems to give me @samp{@r{(empty)}}, which comes out as `(empty)'
with the apostrophes in @samp and the (empty) in @r.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-06-13 19:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 19:53 Daniel Jacobowitz
2006-06-13  8:43 ` Nathan Sidwell
2006-06-13 13:07   ` Daniel Jacobowitz
2006-06-13 18:41     ` Eli Zaretskii
2006-06-13 18:43       ` Daniel Jacobowitz
2006-06-20 20:51         ` Daniel Jacobowitz
2006-06-21  3:14           ` Eli Zaretskii
2006-06-21 14:44             ` Daniel Jacobowitz
2006-06-13 13:38 ` Nathan Sidwell
2006-06-13 13:44   ` Daniel Jacobowitz
2006-06-13 13:46     ` Nathan Sidwell
2006-06-13 18:23 ` Eli Zaretskii
2006-06-13 18:35   ` Daniel Jacobowitz
2006-06-13 18:45     ` Eli Zaretskii
2006-06-13 19:16       ` Daniel Jacobowitz [this message]
2006-06-14  3:26         ` Eli Zaretskii
2006-06-20 20:42           ` Daniel Jacobowitz
2006-06-21  3:11             ` 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=20060613191654.GA16866@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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