From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
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 20:07:51 +0300 [thread overview]
Message-ID: <83o8dj7s48.fsf@gnu.org> (raw)
In-Reply-To: <0ECAF0D9-7D8C-4BAA-AFFE-B76634BD0B28@gmail.com> (message from Howard Melman on Sun, 9 May 2021 12:41:17 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Sun, 9 May 2021 12:41:17 -0400
>
>
> The documentation of function text-property-search-forward says:
>
> If not found, return nil and don’t move point.
>
> Yet I find it moves point to eob.
>
> To reproduce in emacs -Q, with point at beginning of *scratch* buffer with
> text in it, eval:
>
> (require 'text-property-search)
> (text-property-search-forward 'facet 'foo)
>
> point is moved to end of buffer.
How do you know it "didn't find" in this case? what was the value it
returned?
next prev parent reply other threads:[~2021-05-09 17:07 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 [this message]
[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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o8dj7s48.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48317@debbugs.gnu.org \
--cc=hmelman@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 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.