From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Matthias Meulien <matthias.meulien@delair-tech.com>,
25905@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#25905: 25.1; Can't find regexp and replace in SVG files
Date: Mon, 14 Dec 2020 21:55:08 +0200 [thread overview]
Message-ID: <87mtyg2ryb.fsf@mail.linkov.net> (raw)
In-Reply-To: <875z541hpt.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 14 Dec 2020 17:21:34 +0100")
>> Why only for query-replace? Shouldn't isearch
>> display an image file as text for search too?
>
> Hm... how would that work? I'd assume that if you're already in a
> buffer with an image, you'd switch to the text version before doing an
> isearch. So I don't quite see how this connects to the
> dired-do-query-replace-regexp command...
There is also the dired-do-isearch command that searches in marked files.
OTOH, when such "making text visible to search" would be implemented
for isearch, then it will be used automatically by query-replace that
relies on the same search functions.
next prev parent reply other threads:[~2020-12-14 19:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 0:20 bug#25905: 25.1; Can't find regexp and replace in SVG files Matthias Meulien
2020-12-12 19:56 ` Lars Ingebrigtsen
2020-12-12 20:24 ` Juri Linkov
2020-12-13 12:35 ` Lars Ingebrigtsen
2020-12-12 21:29 ` Dmitry Gutov
2020-12-13 12:42 ` Lars Ingebrigtsen
2020-12-13 18:39 ` Dmitry Gutov
2020-12-13 20:02 ` Juri Linkov
2020-12-14 16:21 ` Lars Ingebrigtsen
2020-12-14 19:55 ` Juri Linkov [this message]
2020-12-15 6:34 ` Lars Ingebrigtsen
2020-12-15 20:42 ` Juri Linkov
2020-12-17 22:03 ` Juri Linkov
2020-12-18 8:46 ` Juri Linkov
2020-12-18 10:02 ` Lars Ingebrigtsen
2020-12-19 20:29 ` Juri Linkov
2020-12-23 7:13 ` Lars Ingebrigtsen
2020-12-23 9:30 ` 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=87mtyg2ryb.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=25905@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=matthias.meulien@delair-tech.com \
/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.