bug-gnu-emacs
[Top][All Lists]
Advanced

[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: Juri Linkov
Subject: bug#67161: 30.0.50; [PATCH] Add option `dired-filename-display-length'
Date: Tue, 21 Nov 2023 19:12:10 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu)

>> > I think the idea is that matching invisible text is somewhat
>> > inconvenient, so it's better to temporarily reveal/open that text.
>> > But I think it points to an bug in Isearch: when `isearch-invisible` is
>> > `open` we should match text inside invisible text, regardless if we can
>> > reveal/open that invisible text or not.  IOW `open` should find the
>> > same matches as `t`, the only difference being that it additionally
>> > (tries to) reveal/open the text.
>>
>> This could be a new value like `open-or-match` with a trivial change:
>>
>> @@ -3899,6 +3899,9 @@ isearch-filter-visible
>>  of what `isearch-range-invisible' says."
>>    (and (not (text-property-not-all beg end 'inhibit-isearch nil))
>>         (or (eq search-invisible t)
>> +           (when (eq search-invisible 'open-or-match)
>> +             (isearch-range-invisible beg end)
>> +             t)
>>             (not (isearch-range-invisible beg end)))))
>>
>> But I doubt that it could be enabled by default because in many cases
>> it's too confusing for users to stop at a match that is not visible.
>
> Isn't it possible to unhide the invisible text by temporarily
> manipulating buffer-invisibility-spec?

Do you mean unhiding text properties?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]