unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry EMERY <thierryalemery@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55768@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#55768: 26.3; isearch highlighting in dired
Date: Fri, 3 Jun 2022 09:23:12 +0200	[thread overview]
Message-ID: <CAM75=5AhZS5-jdxW63A8OyPT=PDg1spGyYapiahMoX93cusKNw@mail.gmail.com> (raw)
In-Reply-To: <87leuebeyj.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

(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))

If the text property `invisible' has another symbol than t as value and
`buffer-invisibility-spec' is a list (which is the case in dired, see
below), then the text will only be invisible if that symbol is currently
part of `buffer-invisibility-spec' (and that is used by
`dired-hide-details-mode').

buffer-invisibility-spec is a variable defined in ‘C source code’.
Its value is (t)
Local in buffer lisp; global value is t

  Automatically becomes buffer-local when set.

Documentation:
Invisibility spec of this buffer.
The default is t, which means that text is invisible if it has a non-nil
‘invisible’ property.
This variable can also be a list.  The list can have two kinds of elements:
‘ATOM’ and ‘(ATOM . ELLIPSIS)’.  A text character is invisible if its
‘invisible’ property is ‘ATOM’, or has an ‘invisible’ property that is a
list
that contains ‘ATOM’.
If the ‘(ATOM . ELLIPSIS)’ form is used, and ‘ELLIPSIS’ is non-nil, an
ellipsis will be displayed after the invisible characters.
Setting this variable is very fast, much faster than scanning all the text
in
the buffer looking for properties to change.

[-- Attachment #2: Type: text/html, Size: 1536 bytes --]

  reply	other threads:[~2022-06-03  7:23 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 [this message]
2022-06-03  7:42     ` Thierry EMERY
2022-06-04 11:24     ` Lars Ingebrigtsen
2022-06-28 16:53       ` Juri Linkov
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='CAM75=5AhZS5-jdxW63A8OyPT=PDg1spGyYapiahMoX93cusKNw@mail.gmail.com' \
    --to=thierryalemery@gmail.com \
    --cc=55768@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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).