From: Eli Zaretskii <eliz@gnu.org>
To: Geoffrey Teale <tealeg@gmail.com>, Juri Linkov <juri@linkov.net>
Cc: 70832@debbugs.gnu.org
Subject: bug#70832: 30.0.50; repunctuate-sentences should respect sentence-end-double-space
Date: Sat, 11 May 2024 12:37:13 +0300 [thread overview]
Message-ID: <86eda83d12.fsf@gnu.org> (raw)
In-Reply-To: <CALx3QY_MBcRnrvo3M8+Tb-vYN9fKED_w4cF-5mxsdyCJLjMxzA@mail.gmail.com> (message from Geoffrey Teale on Wed, 8 May 2024 12:21:50 +0200)
severity 70832 wishlist
thanks
> From: Geoffrey Teale <tealeg@gmail.com>
> Date: Wed, 8 May 2024 12:21:50 +0200
>
> In paragraphs.el there is a variable 'sentence-end-doulbe-space` that indicates where we should expect
> sentences to end with one or two spaces after a period. In the same file a command is provided called
> "repunctuate-sentences", which steadfastly ignores the value of this variable and expands all single-space
> endings to two-space endings.
>
> It strikes me that the naming of this command does not imply that it will insist on two-spaces (even if the docs
> say so), and it would be more sensible and offer more utility for it to respect the users wishes. As the variable
> default to `t, changing this function would have zero impact on the default behaviour.
Patches to allow repunctuate-sentences heed the value of
sentence-end-double-space are welcome.
next prev parent reply other threads:[~2024-05-11 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 10:21 bug#70832: 30.0.50; repunctuate-sentences should respect sentence-end-double-space Geoffrey Teale
2024-05-11 9:37 ` Eli Zaretskii [this message]
2024-05-12 6:58 ` Juri Linkov
2024-05-12 7:08 ` Eli Zaretskii
2024-05-12 16:30 ` Juri Linkov
2024-05-12 17:20 ` Eli Zaretskii
2024-05-13 6:50 ` Juri Linkov
2024-05-13 7:39 ` Geoffrey Teale
2024-05-25 7:48 ` 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
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=86eda83d12.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70832@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=tealeg@gmail.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).