From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc] Mention accelerated watchpoint conditions in the gdb manual
Date: Tue, 17 Aug 2010 20:36:00 -0000 [thread overview]
Message-ID: <83sk2dq8sq.fsf@gnu.org> (raw)
In-Reply-To: <1282076384.2606.715.camel@hactar>
> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Tue, 17 Aug 2010 17:19:43 -0300
>
> > > +@smallexample
> > > +(@value{GDBP}) watch @var{ADDRESS|VARIABLE} if @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
> > > +@end smallexample
> >
> > Please break the long line in two: it's too long and will overflow the
> > page boundary in the printed manual.
>
> I had tested this on gdb.pdf and the generated line is shorter than the
> surrounding paragraphs.
It depends on the fonts used by TeX. In general, any line in
@smallexample that is longer than 72 characters is unsafe.
> What about this version?
It's fine, thanks.
next prev parent reply other threads:[~2010-08-17 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 19:40 Thiago Jung Bauermann
2010-08-17 19:57 ` Eli Zaretskii
2010-08-17 20:19 ` Thiago Jung Bauermann
2010-08-17 20:36 ` Eli Zaretskii [this message]
2010-08-18 18:14 ` Thiago Jung Bauermann
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=83sk2dq8sq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bauerman@br.ibm.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