From: Daniel Koning <dk@danielkoning.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefan@marxist.se>,
41761@debbugs.gnu.org, pipcet@gmail.com
Subject: bug#41761: [PATCH] bug#41761: 28.0.50; M-x count-words counts words only up to a field boundary
Date: Fri, 14 Aug 2020 13:48:44 -0500 [thread overview]
Message-ID: <m2imdl83n7.fsf@danielkoning.com> (raw)
In-Reply-To: <83imdllc2l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Aug 2020 14:08:18 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> This change in behavior should be in NEWS. And I'm not sure
> we shouldn't provide an optional knob to get back the old behavior:
> some package or user might rely on it.
I don't think I agree. The "new" behavior is what the documentation
described to begin with. And it's a complexity burden to solder new
switches onto these simple functions -- more burdensome (I say) than
trusting users to impose the constraint by hand if that's what they
want. Something like:
(count-words start (min end (field-end start t)))
Daniel
next prev parent reply other threads:[~2020-08-14 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:52 bug#41761: 28.0.50; M-x count-words counts words only up to a field boundary Pip Cet
2020-06-10 20:15 ` bug#41761: [PATCH] " Daniel Koning
2020-08-14 9:58 ` Stefan Kangas
2020-08-14 11:08 ` Eli Zaretskii
2020-08-14 18:48 ` Daniel Koning [this message]
2020-08-14 19:15 ` Eli Zaretskii
2020-08-14 19:44 ` Daniel Koning
2020-08-15 6:30 ` Eli Zaretskii
2020-08-14 23:06 ` Stefan Kangas
2020-08-15 16:28 ` Eli Zaretskii
2020-08-15 17:44 ` Daniel Koning
2020-08-15 17:48 ` Eli Zaretskii
2020-08-15 19:44 ` Daniel Koning
2020-08-16 14:12 ` Eli Zaretskii
2020-08-16 19:04 ` Daniel Koning
2020-08-16 19:27 ` Eli Zaretskii
2020-08-16 19:37 ` Daniel Koning
2020-08-17 13:51 ` Stefan Kangas
2020-08-17 16:12 ` 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=m2imdl83n7.fsf@danielkoning.com \
--to=dk@danielkoning.com \
--cc=41761@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pipcet@gmail.com \
--cc=stefan@marxist.se \
/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).