From: Eli Zaretskii <eliz@gnu.org>
To: Brian Green <briandg@gmail.com>
Cc: 72704@debbugs.gnu.org, juri@linkov.net, rms@gnu.org,
joseph@breatheoutbreathe.in
Subject: bug#72704: 29.4; repunctuate-sentences ignores NO-QUERY
Date: Sat, 24 Aug 2024 12:33:12 +0300 [thread overview]
Message-ID: <86wmk6mfjb.fsf@gnu.org> (raw)
In-Reply-To: <CAJaEi0eJb84FmyNR544f8pVgtsmK5JJF71uNGxiose--esF2cQ@mail.gmail.com> (message from Brian Green on Sat, 24 Aug 2024 01:29:11 -0700)
> From: Brian Green <briandg@gmail.com>
> Date: Sat, 24 Aug 2024 01:29:11 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, 72704@debbugs.gnu.org, juri@linkov.net
>
> I submitted this "bug" report because I mis-interpreted the docstring,
> and because I was approaching this command with a preconceived idea
> about how it should work. I think Eli is right. I can't think of a
> good reason why I would need to stipulate a certain behavior before
> calling the command which I can already get at any point while the
> command is running.
The doc string indeed could use some improvements, at least in stating
explicitly what happens in interactive usage and what only when called
from Lisp.
next prev parent reply other threads:[~2024-08-24 9:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 20:14 bug#72704: 29.4; repunctuate-sentences ignores NO-QUERY Brian Green
2024-08-19 4:48 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-19 6:52 ` Juri Linkov
2024-08-24 3:00 ` Richard Stallman
2024-08-24 6:18 ` Eli Zaretskii
2024-08-27 13:06 ` Richard Stallman
2024-08-27 13:53 ` Eli Zaretskii
2024-08-30 2:32 ` Richard Stallman
2024-08-30 6:40 ` Eli Zaretskii
2024-08-27 13:06 ` Richard Stallman
2024-08-24 6:30 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 6:53 ` Visuwesh
2024-08-24 7:51 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 7:28 ` Eli Zaretskii
2024-08-24 7:54 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 8:29 ` Brian Green
2024-08-24 9:33 ` Eli Zaretskii [this message]
2024-08-24 17:09 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 18:23 ` Brian Green
2024-08-24 19:18 ` Brian Green
2024-08-24 19:41 ` Brian Green
2024-08-25 2:23 ` Visuwesh
2024-08-25 16:53 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 9:23 ` Eli Zaretskii
2024-08-31 12:19 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 12:39 ` Eli Zaretskii
2024-08-31 15:50 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 16:08 ` Eli Zaretskii
2024-08-31 17:26 ` Brian Green
2024-08-25 6:51 ` Juri Linkov
2024-08-25 15:11 ` Joseph Turner 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
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=86wmk6mfjb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72704@debbugs.gnu.org \
--cc=briandg@gmail.com \
--cc=joseph@breatheoutbreathe.in \
--cc=juri@linkov.net \
--cc=rms@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).