From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
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 11:35:01 +0200 [thread overview]
Message-ID: <87ef04u3ay.fsf@web.de> (raw)
In-Reply-To: <834l10oj0n.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Sep 2019 11:52:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> . What is the reason for having VALUE an optional argument? Is it a
> frequent/useful operation to look for a VALUE of nil?
I also wondered about the optional args, semantics is a bit unusual:
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. I needed to read it
twice.
Michael.
next prev parent reply other threads:[~2019-09-25 9:35 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 [this message]
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
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
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=87ef04u3ay.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=37488@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.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).