From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#37488: 27.0.50; Inconsistent naming of arg of `text-property-search-forward' and `-backward' Date: Wed, 25 Sep 2019 18:01:34 +0300 Message-ID: <83sgokmnch.fsf@gnu.org> References: <87y2yfo8fv.fsf@web.de> <834l10oj0n.fsf@gnu.org> <87lfucv7n5.fsf@gnus.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="138605"; mail-complaints-to="usenet@blaine.gmane.org" Cc: michael_heerdegen@web.de, lekktu@gmail.com, 37488@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Sep 25 17:14:20 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iD8zj-000Zvm-KJ for geb-bug-gnu-emacs@m.gmane.org; Wed, 25 Sep 2019 17:14:19 +0200 Original-Received: from localhost ([::1]:53478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iD8zh-0004kv-Vn for geb-bug-gnu-emacs@m.gmane.org; Wed, 25 Sep 2019 11:14:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57666) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iD8nr-0000ra-J3 for bug-gnu-emacs@gnu.org; Wed, 25 Sep 2019 11:02:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iD8nq-0004fN-7C for bug-gnu-emacs@gnu.org; Wed, 25 Sep 2019 11:02:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33499) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iD8nq-0004fE-48 for bug-gnu-emacs@gnu.org; Wed, 25 Sep 2019 11:02:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iD8np-0001hZ-VE for bug-gnu-emacs@gnu.org; Wed, 25 Sep 2019 11:02:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 25 Sep 2019 15:02:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37488 X-GNU-PR-Package: emacs Original-Received: via spool by 37488-submit@debbugs.gnu.org id=B37488.15694237206488 (code B ref 37488); Wed, 25 Sep 2019 15:02:01 +0000 Original-Received: (at 37488) by debbugs.gnu.org; 25 Sep 2019 15:02:00 +0000 Original-Received: from localhost ([127.0.0.1]:42320 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iD8nn-0001g4-N3 for submit@debbugs.gnu.org; Wed, 25 Sep 2019 11:02:00 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49112) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iD8nl-0001b9-5U for 37488@debbugs.gnu.org; Wed, 25 Sep 2019 11:01:57 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iD8nf-0004az-1l; Wed, 25 Sep 2019 11:01:51 -0400 Original-Received: from [176.228.60.248] (port=3226 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iD8ne-0000wX-Bg; Wed, 25 Sep 2019 11:01:50 -0400 In-reply-to: <87lfucv7n5.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 25 Sep 2019 15:15:58 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:167178 Archived-At: > From: Lars Ingebrigtsen > Cc: Juanma Barranquero , 37488@debbugs.gnu.org, > michael_heerdegen@web.de > Date: Wed, 25 Sep 2019 15:15:58 +0200 > > Eli Zaretskii writes: > > > . The original doc string said about nil as PREDICATE: > > > > `nil' means almost the same as \"not equal\", but will also > > end the match if the value of PROPERTY changes. > > > > What does it mean to "end the match if the value changes"? The > > text went on to say "See the manual for extensive examples", but > > the manual doesn't mention this aspect of nil, it just says "not > > equal". > > If point is inside a region where PROPERTY has a non-nil value, using > nil as the predicate will end the search when PROPERTY changes value. OK, but then it should be obvious, and explicitly mentioning that in the doc string just makes it more confusing. Or am I missing something? > > . The doc string stated: > > > > If NOT-CURRENT, if the match is under point, it will not be > > returned, but instead the next instance is returned, if any. > > > > But the code, AFAIU, just checks whether the value of PROPERTY at > > point matches that of the found region, which doesn't necessarily > > mean point is part of the region, it could just mean there are two > > regions with matching values of PROPERTY, and point belongs to one > > of them. Right? > > I'm not sure I understand the question... The code doesn't seem to make sure point is inside the same region as the one found by the initial attempt, it just compares the values of PROPERTY at point and in the found region, and if they match, it looks for another region. Is that a correct description of what the code does when NOT-CURRENT is non-nil? If the description is correct, then the doc string doesn't describe what the code does accurately. > What it's meant to do is basically how TAB works in buttons, which is a > common use case. If you're looking for "o", and point is where "|" is > below, then it'll find the last "oo" section after the x-es: > > oo|oxxxxxoo What does "o" stand for in this case? > > . What is the reason for having VALUE an optional argument? Is it a > > frequent/useful operation to look for a VALUE of nil? > > If PREDICATE is nil, then having to use an explicit nil VALUE isn't > necessary. I don't understand how this answers my questions.