From: Eli Zaretskii <eliz@gnu.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: simenheg@runbox.com, manuel@ledu-giraud.fr, 62027@debbugs.gnu.org
Subject: bug#62027: Subject: 29.0.60; Breaking change in forward-sentence/backward-sentence
Date: Tue, 07 Mar 2023 15:07:24 +0200 [thread overview]
Message-ID: <834jqw7lrn.fsf@gnu.org> (raw)
In-Reply-To: <m1zg8oomb2.fsf@yahoo.es> (bug-gnu-emacs@gnu.org)
> Cc: simenheg@runbox.com, manuel@ledu-giraud.fr
> Date: Tue, 07 Mar 2023 12:03:45 +0100
> From: Daniel Martín via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
> > Simen Heggestøyl <simenheg@runbox.com> writes:
> >
> > [...]
> >
> >> Or could perhaps the change in return values from
> >> `forward-sentence'/`backward-sentence' be reverted to old behavior, and
> >> the counting logic be left to `count-sentences' instead?
> >
> > Hi Simen,
> >
> > Yes maybe I could change `count-sentences' a bit to do this. What
> > others think of such a change?
>
> I'm all for reverting to the traditional return values of the sentence
> commands, specially if they don't complicate the new command much. The
> return value was not documented, but Hyrum's Law
> (https://www.hyrumslaw.com/) tells us that there is an unknown amount of
> code out there that depends on the traditional return value, anyway.
Agreed.
next prev parent reply other threads:[~2023-03-07 13:07 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jqw7lrn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62027@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 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.