[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#37496: 27.0.50; C-s failing to search
From: |
Jean Louis |
Subject: |
bug#37496: 27.0.50; C-s failing to search |
Date: |
Thu, 26 Sep 2019 10:54:34 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
* Eli Zaretskii <eliz@gnu.org> [2019-09-26 10:07]:
> You could edebug-defun in wdired-isearch-filter-read-only, and see if
> it gets invoked when you type C-s, and if so, whether it somehow
> thinks every search hit is to be skipped. Can you do that?
When it happens, that I just invokie (edebug-defun) in the buffer?
Let me say that search is lost after doing my activities, and I do not
search during editing of Dired buffers, so not that I attempted it
during Wdired. Usually I finish Wdired with C-c C-c and then I move to
some other directory.
I will try to invoke edebug, but how to invoke it exactly?
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/24
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/09/24
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/24
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/25
- 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 <=
- 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, 2019/09/28
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/09/28