[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#37496: 27.0.50; C-s failing to search
From: |
Eli Zaretskii |
Subject: |
bug#37496: 27.0.50; C-s failing to search |
Date: |
Sat, 28 Sep 2019 16:40:56 +0300 |
> Date: Sat, 28 Sep 2019 14:19:18 +0200
> From: Jean Louis <bugs@gnu.support>
> Cc: 37496@debbugs.gnu.org
>
> > If Edebug doesn't kick in, it might mean the
> > wdired-isearch-filter-read-only function is not invoked in this
> > scenario, i.e. my theory is incorrect, and some other factor is at
> > work here.
>
> Am I in wdired if I finish editing with C-c C-c ?
I don't know, and I don't think it matters.
> Search is not working in any buffers, or newly created buffers,
> overall search stops working. When that happens I am not in Wdired. I
> just say I used often Wdired before it happenes.
Yes, I understand that much. My theory was that somehow the isearch
filter set by Wdired stays in effect even after you exit Wdired, and
that the filter somehow decides that every search match should be
skipped.
- bug#37496: 27.0.50; C-s failing to search, (continued)
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/26
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/28
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/28
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/28
- bug#37496: 27.0.50; C-s failing to search,
Eli Zaretskii <=
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/28