From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 37496@debbugs.gnu.org
Subject: bug#37496: 27.0.50; C-s failing to search
Date: Thu, 26 Sep 2019 10:39:10 +0300 [thread overview]
Message-ID: <834l0zmrq9.fsf@gnu.org> (raw)
In-Reply-To: <20190926072212.GG4022@protected.rcdrun.com> (message from Jean Louis on Thu, 26 Sep 2019 09:22:13 +0200)
> Date: Thu, 26 Sep 2019 09:22:13 +0200
> From: Jean Louis <bugs@gnu.support>
> Cc: 37496@debbugs.gnu.org
>
> I invoke C-s, and there is minibuffer, I am entering any term and no
> term can be found in any of the buffers.
Even if you create a new buffer with "C-x b", type some text into it,
and then try to search for that text in that buffer?
> What I can say is that I am doing a lot of editing with Wdired and
> that before, when I was not doing much with Wdired, I have never seen
> this taking place.
Could be related to isearch-filter-predicate set up by wdired.el,
perhaps?
My first suggestion is to stop using Wdired for a while, and see if
the problem never happens then.
next prev parent reply other threads:[~2019-09-26 7:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:51 bug#37496: 27.0.50; C-s failing to search Jean Louis
2019-09-24 10:38 ` Eli Zaretskii
2019-09-24 11:32 ` Jean Louis
2019-09-25 20:45 ` Jean Louis
2019-09-26 7:02 ` Eli Zaretskii
2019-09-26 7:22 ` Jean Louis
2019-09-26 7:39 ` Eli Zaretskii [this message]
2019-09-26 7:50 ` Jean Louis
2019-09-26 8:06 ` Eli Zaretskii
2019-09-26 8:54 ` Jean Louis
2019-09-26 9:50 ` Eli Zaretskii
2019-09-28 11:06 ` Jean Louis
2019-09-28 12:13 ` Eli Zaretskii
2019-09-28 12:19 ` Jean Louis
2019-09-28 13:40 ` Eli Zaretskii
2019-09-28 15:08 ` Jean Louis
2019-10-03 18:32 ` Jean Louis
2019-10-03 18:56 ` Eli Zaretskii
2019-10-03 19:14 ` Jean Louis
2019-10-03 19:46 ` Eli Zaretskii
2019-10-03 19:51 ` Jean Louis
2019-10-04 7:17 ` Eli Zaretskii
2019-10-04 14:33 ` Jean Louis
2019-10-07 18:17 ` Juri Linkov
2019-10-08 12:16 ` Jean Louis
2020-01-28 0:12 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l0zmrq9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37496@debbugs.gnu.org \
--cc=bugs@gnu.support \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.