[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length'
From: |
Eli Zaretskii |
Subject: |
bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length' |
Date: |
Mon, 20 Nov 2023 20:42:30 +0200 |
> From: Juri Linkov <juri@linkov.net>
> Cc: Liu Hui <liuhui1610@gmail.com>, stefankangas@gmail.com,
> monnier@iro.umontreal.ca, 67161@debbugs.gnu.org
> Date: Mon, 20 Nov 2023 19:54:27 +0200
>
> >> Therefore, I would like to change
> >>
> >> (put-text-property ell-beg (point) 'invisible 'dired-filename-hide)
> >>
> >> to
> >>
> >> (let ((ov (make-overlay ell-beg (point))))
> >> (overlay-put ov 'invisible 'dired-filename-hide)
> >> (overlay-put ov 'isearch-open-invisible t)
> >> (overlay-put ov 'evaporate t))
> >
> > Juri, this seems to be a usability bug? Why does Isearch only look
> > into invisible overlay properties, but not text properties? IOW, why
> > doesn't "M-s i" set the value of isearch-invisible to t, not 'open'?
> > Or maybe 'open' should also search inside text properties, not just
> > overlays? In any case, the differences between properties and
> > overlays is unusual and IMO a misfeature. Can this be fixed?
>
> I recall Ihor implemented the revealing of invisible text properties
> for Org-mode when overlays were very slow. But now overlays are
> optimized, so Liu is absolutely right that better to use overlays.
That might be so, but I was asking about Isearch being able to find
matches inside invisible text, not about the Dired feature. Why
cannot a user tell Isearch to find text that is invisible due to text
properties?
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', (continued)
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Liu Hui, 2023/11/15
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/15
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Liu Hui, 2023/11/16
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/16
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Liu Hui, 2023/11/18
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/18
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Drew Adams, 2023/11/18
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Liu Hui, 2023/11/19
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/20
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Juri Linkov, 2023/11/20
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length',
Eli Zaretskii <=
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Stefan Monnier, 2023/11/20
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/20
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Juri Linkov, 2023/11/21
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/21
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Juri Linkov, 2023/11/21
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Drew Adams, 2023/11/20
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Liu Hui, 2023/11/22
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/25
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Juri Linkov, 2023/11/25
- bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length', Eli Zaretskii, 2023/11/25