From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: stabs.texinfo update for macro define/undefine
Date: Tue, 31 Oct 2006 22:39:00 -0000 [thread overview]
Message-ID: <u4ptk6rg2.fsf@gnu.org> (raw)
In-Reply-To: <200610311418.k9VEI3pN004364@mailhub.lss.emc.com> (message from David Taylor on Tue, 31 Oct 2006 09:18:03 -0500)
> cc: gdb-patches@sourceware.org
> Date: Tue, 31 Oct 2006 09:18:03 -0500
> From: David Taylor <dtaylor@emc.com>
>
> You mentioned it, but I guess I misunderstood. I ran both `make dvi'
> and `make info' and looked at the resulting files. The info file
> stayed in fewer than 80 columns; I didn't see any TeX complaints about
> an overfull hbox, nor did the dvi file have a black box on any of
> those lines. So, I guessed that they looked too long but were
> actually okay.
Maybe due to whitespace TeX succeeded to squeeze them in.
> In the future, how should I test to make sure that the lines are not
> too long?
Any line longer than 64 characters in an @example should be shortened.
> For this, how about:
>
> @example
> .stabs "NONE 42",54,0,1,0
> .stabs "TWO(a,b) (a + (a) + 2 * b)",54,0,2,0
> .stabs "ONE(c) (c + 19)",54,0,3,0
> .stabs "ONE",58,0,10,0
> .stabs "ONE(c) (c + 23)",54,0,11,0
> @end example
>
> NOTE: In the example above, @code{54} is @code{N_MAC_DEFINE} and @code{58}
> is @code{N_MAC_UNDEF}.
>
> ? This is the text in the patch attached below.
This is fine; it's exactly what I was suggesting.
> > With these changes, this can go in. Thanks.
>
> Thanks. I don't have write after approval privileges.
I committed the patch for you. Thanks again for working on this.
next prev parent reply other threads:[~2006-10-31 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610251931.k9PJVRDO011265@mailhub.lss.emc.com>
[not found] ` <ud58guoa6.fsf@gnu.org>
2006-10-30 22:25 ` David Taylor
2006-10-31 4:19 ` Eli Zaretskii
2006-10-31 14:18 ` David Taylor
2006-10-31 22:39 ` Eli Zaretskii [this message]
2006-10-31 23:23 ` Jim Blandy
2006-11-01 3:21 ` David Taylor
2006-11-01 19:32 ` Jim Blandy
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=u4ptk6rg2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@emc.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