From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37496@debbugs.gnu.org
Subject: bug#37496: 27.0.50; C-s failing to search
Date: Sat, 28 Sep 2019 14:19:18 +0200 [thread overview]
Message-ID: <20190928121918.GB31210@protected.rcdrun.com> (raw)
In-Reply-To: <83tv8whb5f.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2019-09-28 14:13]:
> > Date: Sat, 28 Sep 2019 13:06:44 +0200
> > From: Jean Louis <bugs@gnu.support>
> > Cc: 37496@debbugs.gnu.org
> >
> > I have tried this but I did not see nothing happening, no debug,
> > something wrong on my side. I am waiting for that to happen again so
> > that I try this again.
>
> 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 ?
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.
Jean
next prev parent reply other threads:[~2019-09-28 12:19 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190928121918.GB31210@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=37496@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).