Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] add obstacks to gdbint.texi
Date: Wed, 11 Feb 2004 06:09:00 -0000	[thread overview]
Message-ID: <ur7x2p2pv.fsf@elta.co.il> (raw)
In-Reply-To: <16425.16481.598965.602145@localhost.redhat.com> (message from Elena Zannoni on Tue, 10 Feb 2004 15:34:41 -0500)

> From: Elena Zannoni <ezannoni@redhat.com>
> Date: Tue, 10 Feb 2004 15:34:41 -0500
>  > > 
>  > > Ok, is there something in .emacs that I should set to get this done when
>  > > I do an 'esc-q' for instance? 
>  > 
>  > It does that for me by default.  If it doesn't for you, perhaps you
>  > have sentence-end-double-space set to nil somehow.
> 
> Something screwy with my emacs, no doubt. But the variable is set
> correctly.

Then perhaps you have some non-default setting for sentence-end.

> ok. Also corrected the lie about xmalloc/xfree.
> 
> Index: gdbint.texinfo

This version is fine, I have only one more suggestion:

> +@value{GDBN} uses various features provided by the @code{libiberty}
> +library, for instance the C++ demangler, the @acronym{IEEE} floating

The "C++" thingie will look prettier in the printed manual if you
spell it as "C@t{++}", as then TeX will typeset the "++" part with a
typewriter face, as it does with the C operator "++" in a code
fragment.

Thanks.


  reply	other threads:[~2004-02-11  6:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 17:31 Elena Zannoni
2004-02-10 19:04 ` Eli Zaretskii
2004-02-10 19:51   ` Elena Zannoni
2004-02-10 20:06     ` Eli Zaretskii
2004-02-10 20:38       ` Elena Zannoni
2004-02-11  6:09         ` Eli Zaretskii [this message]
2004-02-11 15:41           ` Elena Zannoni
2004-02-11 19:27             ` Eli Zaretskii
2004-02-10 19:30 ` Daniel Jacobowitz
2004-02-10 20:06   ` Elena Zannoni
2004-02-10 20:11     ` Daniel Jacobowitz

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=ur7x2p2pv.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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