From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: michael_heerdegen@web.de, lekktu@gmail.com, 37488@debbugs.gnu.org
Subject: bug#37488: 27.0.50; Inconsistent naming of arg of `text-property-search-forward' and `-backward'
Date: Wed, 25 Sep 2019 18:05:21 +0300 [thread overview]
Message-ID: <83r244mn66.fsf@gnu.org> (raw)
In-Reply-To: <87h850v7l4.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 25 Sep 2019 15:17:11 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, lekktu@gmail.com, 37488@debbugs.gnu.org
> Date: Wed, 25 Sep 2019 15:17:11 +0200
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> >> > note that PREDICATE -> nil means "not equal", so with VALUE -> nil this
> >> > actually searches for non-nil values of the text property, which is a
> >> > reasonable (and the expected) default behavior.
> >>
> >> Is it? IME, we usually search for a specific value, not for any
> >> value.
> >
> > For me, yes, the function fills a certain gap. But I'm not an expert on
> > that matter.
>
> In my experience, we almost never search for a specific value for a text
> property, but any text that has that property. That's why I added the
> nil PREDICATE to avoid having to supply that awkward lambda into every
> function I wrote...
We have different experiences, then.
In any case, the API uses double negation in the default case (find
text whose value of PROPERTY does NOT match no-value), which is
baaad...
next prev parent reply other threads:[~2019-09-25 15:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 6:03 bug#37488: 27.0.50; Inconsistent naming of arg of `text-property-search-forward' and `-backward' Michael Heerdegen
2019-09-23 7:30 ` Juanma Barranquero
2019-09-23 7:47 ` Michael Heerdegen
2019-09-25 8:52 ` Eli Zaretskii
2019-09-25 9:35 ` Michael Heerdegen
2019-09-25 9:43 ` Eli Zaretskii
2019-09-25 10:16 ` Michael Heerdegen
2019-09-25 10:26 ` Eli Zaretskii
2019-09-25 13:17 ` Lars Ingebrigtsen
2019-09-25 15:05 ` Eli Zaretskii [this message]
2019-09-26 15:13 ` Lars Ingebrigtsen
2019-09-25 13:15 ` Lars Ingebrigtsen
2019-09-25 15:01 ` Eli Zaretskii
2019-09-26 14:42 ` Eli Zaretskii
2019-09-26 15:13 ` Lars Ingebrigtsen
2019-09-26 15:12 ` Lars Ingebrigtsen
2019-09-26 17:05 ` Eli Zaretskii
2019-09-26 19:16 ` Lars Ingebrigtsen
2019-09-26 19:24 ` Eli Zaretskii
2019-09-27 14:15 ` Lars Ingebrigtsen
2019-09-27 14:33 ` Eli Zaretskii
2019-09-27 14:36 ` Lars Ingebrigtsen
2019-09-28 14:45 ` Eli Zaretskii
2019-09-26 5:55 ` Michael Heerdegen
2019-09-26 7:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r244mn66.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37488@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.com \
--cc=michael_heerdegen@web.de \
/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.