unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Geoffrey Teale <tealeg@gmail.com>
Cc: 70832-done@debbugs.gnu.org, juri@linkov.net
Subject: bug#70832: 30.0.50; repunctuate-sentences should respect sentence-end-double-space
Date: Sat, 25 May 2024 10:48:48 +0300	[thread overview]
Message-ID: <8634q61gdb.fsf@gnu.org> (raw)
In-Reply-To: <CALx3QY9DCFp4mLRaXHxSdrT=63VsbzpHQAnbyn0-LdXt-Wjung@mail.gmail.com> (message from Geoffrey Teale on Mon, 13 May 2024 09:39:52 +0200)

> From: Geoffrey Teale <tealeg@gmail.com>
> Date: Mon, 13 May 2024 09:39:52 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 70832@debbugs.gnu.org
> 
>  But the problem is that when a user customized
>  sentence-end-double-space to nil, the user still
>  might want to put two spaces since the docstring says:
> 
>    "Put two spaces at the end of sentences"
> 
>  So using one space will contradict the docstring.
> 
> I was actually aware about the docstring when I raised the bug, but I assumed that changing that docstring
> would be part of the fix.  If I get to the essence of the issue: two spaces at the end of a sentence is no longer
> considered correct in most prose-authoring contexts.  In that sense what I really wanted is the ability to
> automatically remove any such instances from an Org or Markdown file, for example.  When I went looking for
> that in emacs this seemed like the correct tool for the job, and it is a little bit glaring that there's such a
> variable that one can set, but this function, defined in the same file, doesn't respect it.  
> 
> That said, yes of course one could easily use query-replace as suggested above. 

No further comments in 12 days, so I'm now closing this bug.





      reply	other threads:[~2024-05-25  7:48 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
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 [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=8634q61gdb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70832-done@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).