From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55768@debbugs.gnu.org, Thierry EMERY <thierryalemery@gmail.com>
Subject: bug#55768: 26.3; isearch highlighting in dired
Date: Tue, 28 Jun 2022 19:53:55 +0300 [thread overview]
Message-ID: <86tu84ohjw.fsf@mail.linkov.net> (raw)
In-Reply-To: <87mtesacyr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 04 Jun 2022 13:24:12 +0200")
>> (invisible-p (point)) has already been tested in the previous line, but it only tests that
>> there is a text property, not actual invisibility:
>> (defun invisible-p (pos)
>> (get-text-property pos 'invisible))
>
> That's not the definition of invisible-p. It's
>
> DEFUN ("invisible-p", Finvisible_p, Sinvisible_p, 1, 1, 0,
> doc: /* Non-nil if text properties at POS cause text there to be currently invisible.
I checked this again, and I see nothing wrong in the current implementation:
(invisible-p (get-text-property (point) 'invisible))
is a valid call, because the arg of ‘invisible-p’ can be the actual value
of the ‘invisible’ text property.
next prev parent reply other threads:[~2022-06-28 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:22 bug#55768: 26.3; isearch highlighting in dired Thierry EMERY
2022-06-03 3:31 ` Lars Ingebrigtsen
2022-06-03 7:23 ` Thierry EMERY
2022-06-03 7:42 ` Thierry EMERY
2022-06-04 11:24 ` Lars Ingebrigtsen
2022-06-28 16:53 ` Juri Linkov [this message]
2022-06-28 17:22 ` Lars Ingebrigtsen
2022-06-28 17:37 ` Juri Linkov
2022-06-29 9:56 ` Lars Ingebrigtsen
2022-06-29 17:58 ` Juri Linkov
2022-06-30 9:30 ` Lars Ingebrigtsen
2022-06-30 14:37 ` Thierry EMERY
2022-06-30 14:56 ` Lars Ingebrigtsen
2022-06-03 7:55 ` Juri Linkov
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=86tu84ohjw.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=55768@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=thierryalemery@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).