From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Remote "qSupported" features probe
Date: Tue, 20 Jun 2006 20:42:00 -0000 [thread overview]
Message-ID: <20060620204252.GF1453@nevyn.them.org> (raw)
In-Reply-To: <ubqsw4due.fsf@gnu.org>
On Wed, Jun 14, 2006 at 06:26:33AM +0300, Eli Zaretskii wrote:
> > Date: Tue, 13 Jun 2006 15:16:54 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > > 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.
>
> You could use @table @code and add the apostrophes manually where you
> want them.
Turns out that doesn't work either: both @code and @samp have implicit
apostrophes in Info output. So while this looks a little better in the
PDF, it's nasty in Info.
I'm going to leave it as @item, since that's already used in a number
of places throughout this chapter. If we want to improve this later,
we can do it more consistently.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 20:42 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
2006-06-14 3:26 ` Eli Zaretskii
2006-06-20 20:42 ` Daniel Jacobowitz [this message]
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=20060620204252.GF1453@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