all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: 71865@debbugs.gnu.org
Subject: bug#71865: [PATCH] New user option `fill-sentence-end-double-space`
Date: Mon, 1 Jul 2024 16:02:28 -0700	[thread overview]
Message-ID: <CADwFkmmzoMPwB+2v83MVX1+z=R1+uuyvKHcWHExM69ggesKo=A@mail.gmail.com> (raw)
In-Reply-To: <87v81obyp9.fsf@jeremybryant.net>

Jeremy Bryant <jb@jeremybryant.net> writes:

> I tried this example but would be interested in a clearer statement of
> the problem.  Does M-a, M-e not work as intended?

Thanks, and yes indeed, the `M-a' and `M-e' doesn't work as I'd hope if
you evaluate this in emacs -Q:

    (progn (insert "Foo. Bar. Baz.")
           (goto-char (pos-bol))
           (forward-sentence))

Point is now at the third period, after "Baz".

I think that there are some users [this one included] that will want to
set

    (setq sentence-end-double-space nil)

to make point end up at the second period instead, after "Bar", yet they
do _not_ want this paragraph to be refilled to use only one space
between sentences:

    Foo.  Bar.  Baz.

In other words, the problem is that `sentence-end-double-space' controls
both filling and sentence commands.  This rectifies that by introducing
a new variable that allows controlling the filling commands separately.

Does that make the problem more clear?





  reply	other threads:[~2024-07-01 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  1:07 bug#71865: [PATCH] New user option `fill-sentence-end-double-space` Stefan Kangas
2024-07-01 21:16 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-01 23:02   ` Stefan Kangas [this message]
2024-07-06 21:46     ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CADwFkmmzoMPwB+2v83MVX1+z=R1+uuyvKHcWHExM69ggesKo=A@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=71865@debbugs.gnu.org \
    --cc=jb@jeremybryant.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.