From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: fill-paragraph vs. single spaced sentences
Date: Tue, 05 Apr 2005 15:07:32 -0400 [thread overview]
Message-ID: <E1DItOe-0006jK-LL@fencepost.gnu.org> (raw)
In-Reply-To: <87oecu1cvo.fsf@jidanni.org> (message from Dan Jacobson on Tue, 05 Apr 2005 04:54:35 +0800)
OK, I'll (setq sentence-end-double-space nil). Hurmf. Should be the
default. I can't think of any computer language where the amount of
whitespace is relevant, except python. Made sense with .txt files,
but not nowadays for, e.g., HTML.
The main use for the fill commands in programs is when operating on
comments. Our recommended convention is two spaces between sentences,
including in comments.
prev parent reply other threads:[~2005-04-05 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 20:54 fill-paragraph vs. single spaced sentences Dan Jacobson
2005-04-05 19:07 ` Richard Stallman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DItOe-0006jK-LL@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).