From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Document "set/show print frame-arguments"
Date: Sun, 11 Nov 2007 07:48:00 -0000 [thread overview]
Message-ID: <uejexp6jc.fsf@gnu.org> (raw)
In-Reply-To: <20071110181955.GA2141@adacore.com> (message from Joel Brobecker on Sat, 10 Nov 2007 10:19:55 -0800)
> Date: Sat, 10 Nov 2007 10:19:55 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > Please use @dots{} here and elsewhere, it looks better in print.
>
> Should I use that in @smallexample too?
Sure, why not?
> +is replaced by @dots{}. In this case, the example above now becomes:
@code{@dots{}}
Also, there's still one place with only one space after a period that
ends a sentence.
Otherwise, fine with me. Thanks!
next prev parent reply other threads:[~2007-11-11 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 19:13 Joel Brobecker
2007-11-10 11:11 ` Eli Zaretskii
2007-11-10 11:11 ` Eli Zaretskii
2007-11-10 18:20 ` Joel Brobecker
2007-11-11 7:48 ` Eli Zaretskii [this message]
2007-11-12 5:27 ` Joel Brobecker
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=uejexp6jc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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