Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: keiths@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC/MI] Event Records vs Commands
Date: Sat, 15 Jun 2002 11:46:00 -0000	[thread overview]
Message-ID: <jefzzobct0.fsf@sykes.suse.de> (raw)
In-Reply-To: <4634-Sat15Jun2002203052+0300-eliz@is.elta.co.il> ("Eli Zaretskii"'s message of "Sat, 15 Jun 2002 20:30:52 +0300")

"Eli Zaretskii" <eliz@is.elta.co.il> writes:

|> Thanks.  This is approved, but please take care of teh following
|> small problems:
|> 
|> > ! in @value{GDBN}. Events can be generated by any command, whether that command
|> 
|> Please always leave two spaces after a period that ends a sentence.
|> This is important for the printed version to be typeset correctly by
|> TeX.

Actually TeX doesn't care about the extra whitespace, it treats them all
the same.  The real problem is that @value{GDBN} expands to an all-caps
text, which causes TeX to not consider the period to be a sentence end.
All occurences of periods after @value{GDBN} should be replaced by `@.' to
fix this.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2002-06-15 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 22:24 Keith Seitz
2002-06-15 10:33 ` Eli Zaretskii
2002-06-15 11:46   ` Andreas Schwab [this message]
2002-06-15 19:01 ` Andrew Cagney
2002-06-15 19:10   ` Andrew Cagney
2002-06-18 11:34     ` Keith Seitz
2002-06-18 13:43       ` Eli Zaretskii
2002-06-25 20:17       ` Andrew Cagney
2002-06-17 10:25   ` Keith Seitz
2002-06-17 11:28     ` Andrew Cagney

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=jefzzobct0.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@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