From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: simenheg@runbox.com, 62027-done@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#62027: Subject: 29.0.60; Breaking change in forward-sentence/backward-sentence
Date: Wed, 08 Mar 2023 18:51:35 +0200 [thread overview]
Message-ID: <83cz5j425k.fsf@gnu.org> (raw)
In-Reply-To: <87jzzrab9w.fsf@ledu-giraud.fr> (message from Manuel Giraud on Wed, 08 Mar 2023 09:38:03 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: Eli Zaretskii <eliz@gnu.org>, mardani29@yahoo.es,
> 62027-done@debbugs.gnu.org
> Date: Wed, 08 Mar 2023 09:38:03 +0100
>
> Simen Heggestøyl <simenheg@runbox.com> writes:
>
> > Thanks for the quick fix!
> >
> > Should perhaps the return values of
> > `forward-sentence'/`backward-sentence' be documented to prevent this
> > from happening again?
>
> Why not: Hyrum's law might have won here. But OTOH in master,
> 'forward-sentence' is a now call to 'forward-sentence-function' that
> could be changed by the user. Maybe should we document
> 'forward-sentence-default-function'?
I see no reason to document that.
next prev parent reply other threads:[~2023-03-08 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 7:31 bug#62027: Subject: 29.0.60; Breaking change in forward-sentence/backward-sentence Simen Heggestøyl
2023-03-07 9:35 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 11:03 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 13:07 ` Eli Zaretskii
2023-03-07 16:07 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 16:17 ` Eli Zaretskii
2023-03-07 16:42 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 17:19 ` Eli Zaretskii
2023-03-07 19:07 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 19:32 ` Eli Zaretskii
2023-03-08 6:50 ` Simen Heggestøyl
2023-03-08 8:38 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 15:52 ` Drew Adams
2023-03-08 16:52 ` Eli Zaretskii
2023-03-08 17:52 ` Drew Adams
2023-03-08 19:46 ` Eli Zaretskii
2023-03-08 16:51 ` Eli Zaretskii [this message]
2023-03-08 21:02 ` Manuel Giraud 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=83cz5j425k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62027-done@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=mardani29@yahoo.es \
--cc=simenheg@runbox.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).