From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48317@debbugs.gnu.org
Subject: bug#48317: 27.1; text-property-search-forward moves point to end when not found
Date: Sun, 09 May 2021 21:33:49 +0300 [thread overview]
Message-ID: <83fsyv7o4y.fsf@gnu.org> (raw)
In-Reply-To: <8877DDB9-7D2B-4DCC-8374-EB8391134EAC@gmail.com> (message from Howard Melman on Sun, 9 May 2021 14:10:56 -0400)
[Please use Reply All to keep the bug address on the CC list.]
> From: Howard Melman <hmelman@gmail.com>
> Date: Sun, 9 May 2021 14:10:56 -0400
>
> >> #s(prop-match 77 224 nil)
> >>
> >> If I change 'foo to nil it does not move point.
> >
> > So in your original use case it _did_ find a match, which is why it
> > moved point.
>
> I don't think any region in the buffer has the property 'ffffffff let alone
> with the value 'foo so I don't know what it thinks it's found.
What is the difference between "not having a property" and "having a
property with a nil value"?
> I see in the docstring:
>
> If PREDICATE is nil, a value will match if it is non-nil and
> is NOT equal to VALUE.
>
> But I don't think this applies because no region in the buffer has this property.
I'm trying to establish whether this is a documentation bug or a code
bug. For now, I tend to think it's the former.
> Can you reproduce my simple test case?
> Did it find a region with a random property name?
I don't think I understand the question.
Lars, would you please chime in? Since you coded this stuff, I'm sure
you will be able to explain its workings much better.
next prev parent reply other threads:[~2021-05-09 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 16:41 bug#48317: 27.1; text-property-search-forward moves point to end when not found Howard Melman
2021-05-09 17:07 ` Eli Zaretskii
[not found] ` <616F7732-ED83-40F0-A460-9298608EAD91@gmail.com>
2021-05-09 17:48 ` Eli Zaretskii
[not found] ` <8877DDB9-7D2B-4DCC-8374-EB8391134EAC@gmail.com>
2021-05-09 18:33 ` Eli Zaretskii [this message]
2021-05-09 19:48 ` Howard Melman
2021-05-10 9:05 ` Lars Ingebrigtsen
2021-05-10 13:06 ` Howard Melman
2021-05-11 12:32 ` Lars Ingebrigtsen
2021-05-11 12:48 ` Eli Zaretskii
2021-05-11 13:14 ` Lars Ingebrigtsen
2021-05-11 14:20 ` Howard Melman
2021-05-11 16:36 ` Lars Ingebrigtsen
2021-05-11 19:28 ` Howard Melman
2021-05-11 23:18 ` Stephen Berman
2021-05-12 14:16 ` Lars Ingebrigtsen
2021-05-12 16:29 ` Howard Melman
2021-05-12 16:55 ` Lars Ingebrigtsen
[not found] ` <5AA9C2CD-D20B-4B9D-83D6-9002E9396558@gmail.com>
2022-05-13 18:32 ` Howard Melman
2022-05-14 2:19 ` Lars Ingebrigtsen
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=83fsyv7o4y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48317@debbugs.gnu.org \
--cc=hmelman@gmail.com \
--cc=larsi@gnus.org \
/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).