[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, 3 Oct 2019 21:14:33 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
* Eli Zaretskii <eliz@gnu.org> [2019-10-03 20:57]:
> > Date: Thu, 3 Oct 2019 20:32:12 +0200
> > From: Jean Louis <bugs@gnu.support>
> > Cc: 37496@debbugs.gnu.org
> >
> > I could do edebug-defun on isearch-forward or C-s and then I got this
> > below:
> >
> > Debugger entered: nil
> > edebug--display-1(nil 0 before)
> > edebug--display(nil 0 before)
> > edebug-debugger(0 before nil)
> > edebug-before(0)
>
> What commands did you type that yielded this backtrace?
I have turned on edebug-defun on isearch-forward as that is the key
binding on C-s and then I got the above.
> > And I have observed that the isearch-forward stopped functioning after
> > doing not so many editing with C-x C-q, just few. Suddenly I got the
> > problem again.
>
> C-x C-q in what mode? Which command does it run?
In Dired, when I do C-x C-q it invokes dired-toggle-read-only then I
edit the file names in Dired. Sometimes after editing then I cannot
search any more.
I have observed that I could search from menu Edit - Search String
Forward, that one worked well. Only C-s did not work.
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/10/03
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/10/03
- 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/10/03
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/10/03
- bug#37496: 27.0.50; C-s failing to search, Eli Zaretskii, 2019/10/04
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/10/04
- bug#37496: 27.0.50; C-s failing to search, Juri Linkov, 2019/10/07
- bug#37496: 27.0.50; C-s failing to search, Jean Louis, 2019/10/08