From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/i387] Eliminate HOST_*_FORMAT from i387-tdep.c
Date: Mon, 02 Jul 2001 08:55:00 -0000 [thread overview]
Message-ID: <npr8vzqq7q.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <s3ipubkolli.fsf@soliton.wins.uva.nl>
Mark Kettenis <kettenis@science.uva.nl> writes:
> Oh, and I believe the GNU coding standards demand two spaces after a
> full stop, even at the end of a comment.
I didn't know that was part of the standard, but I can give the
rationale:
The Emacs forward- and backward-sentence commands (M-e and M-a) expect
to see two spaces after a full stop, to help them distinguish a period
after an abbreviation from a period marking the end of a sentence.
It's really handy to have those commands work on comments.
next prev parent reply other threads:[~2001-07-02 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 9:53 Andrew Cagney
2001-07-01 5:56 ` Mark Kettenis
2001-07-02 8:55 ` Jim Blandy [this message]
2001-07-03 12:26 ` Russ Allbery
2001-07-04 12:18 ` Andrew Cagney
2001-07-04 14:13 ` Mark Kettenis
2001-07-06 5:52 Michael Elizabeth Chastain
2001-07-06 6:16 ` Eli Zaretskii
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=npr8vzqq7q.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@science.uva.nl \
/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