From: Thierry EMERY <thierryalemery@gmail.com>
To: 55768@debbugs.gnu.org
Subject: bug#55768: 26.3; isearch highlighting in dired
Date: Thu, 2 Jun 2022 17:22:31 +0200 [thread overview]
Message-ID: <CAM75=5C7C7exLLWWA95wY_jzwH8RqEp+xke6XNGcteU0a8FOtA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
Hello,
isearch fails to highlight in dired and displays the following error:
[image: image.png]
As dired sets text property 'invisible to a symbol, either:
'dired-hide-details-detail, 'dired-hide-details-information or
'dired-hide-details-link, in order for isearch to properly highlight the
searched string in a dired buffer, the following patch ought to be applied
to isearch-range-invisible:
diff -u isearch.el~ isearch.el
--- isearch.el~ 2019-09-10 02:32:49.000000000 +0200
+++ isearch.el 2022-06-02 17:13:55.490492201 +0200
@@ -2972,7 +2972,7 @@
;; skip all characters with that same `invisible' property value.
;; Do that over and over.
(while (and (< (point) end) (invisible-p (point)))
- (if (invisible-p (get-text-property (point) 'invisible))
+ (if (member (get-text-property (point) 'invisible)
buffer-invisibility-spec)
(progn
(goto-char (next-single-property-change (point) 'invisible
nil end))
Kind Regards,
Thierry Emery
[-- Attachment #1.2: Type: text/html, Size: 1238 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 2580 bytes --]
next reply other threads:[~2022-06-02 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:22 Thierry EMERY [this message]
2022-06-03 3:31 ` bug#55768: 26.3; isearch highlighting in dired 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
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=5C7C7exLLWWA95wY_jzwH8RqEp+xke6XNGcteU0a8FOtA@mail.gmail.com' \
--to=thierryalemery@gmail.com \
--cc=55768@debbugs.gnu.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).