unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Carlos Ysais <carlos.ysais@yahoo.com>
Cc: 43965@debbugs.gnu.org
Subject: bug#43965: 27.1; An Introduction to Programming in Emacs Lisp
Date: Mon, 12 Oct 2020 23:57:08 -0400	[thread overview]
Message-ID: <E1kSBQy-0006Yo-8k@fencepost.gnu.org> (raw)
In-Reply-To: <480a1ebd-ad02-5695-5a27-340af48197f7@yahoo.com> (bug-gnu-emacs@gnu.org)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > "According to convention, you type two spaces after every sentence".
  > Recently a percentage of people have been using one space instead of
  > two to end sentences. Because it is a matter of preference, it would be
  > nice if one space is included in the regexes shown in this section.

That change would make the sentence commands give incorrect results.
There is a reason the regexp is what it is.

1. If you write two spaces between sentences, it is possible for
Emacs to distinguish sentence ends from abbreviations.  That regexp
is designed to do that.

2. If you write just once spaces between sentences, it is IMpossible for
Emacs to distinguish sentence ends from abbreviations.  No matter what regexp
you use, it can't do this job entirely right.

For users who want to have the sentence commands distinguish abbeviations
properly, there is only one way to get that:
(a) put two spaces between sentences, and
(b) use the current regexp, which matches only two spaces.

Your change would break case 1, and case 2 would still be broken
because case 2 is impossible.

If you want to use case 2, go ahead, but we will not break case 1!

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2020-10-13  3:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <480a1ebd-ad02-5695-5a27-340af48197f7.ref@yahoo.com>
2020-10-12 16:26 ` bug#43965: 27.1; An Introduction to Programming in Emacs Lisp Carlos Ysais via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-13  3:57   ` Richard Stallman [this message]
2020-10-13 12:26   ` Carlos Ysais via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-14  4:43     ` Richard Stallman
2021-10-11 12:53       ` Stefan Kangas
2020-10-14 10:29   ` Carlos Ysais via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-15  3:54     ` Richard Stallman

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=E1kSBQy-0006Yo-8k@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=43965@debbugs.gnu.org \
    --cc=carlos.ysais@yahoo.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.
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).