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: Thu, 30 Jun 2022 16:37:50 +0200	[thread overview]
Message-ID: <CAM75=5CUgvgJh4=+LLBKogL3iKELvJPNb+qudkBUZtBkcTRkNQ@mail.gmail.com> (raw)
In-Reply-To: <87y1xecxbk.fsf@gnus.org>

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

Hello,

Good news: the bug that i had in Emacs 26.3 is not present in 28.1.
With Emacs 28.1 compiled from source and started with "src/emacs -Q" i can
use incremental search (e.g. in dired) including for visible text (found)
or invisible text (not found), and highlighting is correct in all cases.
Also i see in Emacs 28.1 sources that `invisible-p' has been rewritten (in
C), and is more thorough than in 26.3 :-)

Thanks,

Thierry


Le jeu. 30 juin 2022 à 11:31, Lars Ingebrigtsen <larsi@gnus.org> a écrit :

> Juri Linkov <juri@linkov.net> writes:
>
> >> That's true.  Was that the intention here -- first to check invisibility
> >> of both text properties and overlays and then only check invisibility of
> >> text properties?
> >
> > Yep, that is my understanding too: first check both, then each
> separately.
>
> Right.
>
> Anyway, back to the original issue -- Thierry, you reported this problem
> for Emacs 26.3, but do you see it in more recent Emacs versions?
>
> If so, can you give a complete recipe to reproduce it, starting from
> "emacs -Q"?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

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

  reply	other threads:[~2022-06-30 14:37 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
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 [this message]
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=5CUgvgJh4=+LLBKogL3iKELvJPNb+qudkBUZtBkcTRkNQ@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).