From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>,
Tino Calancha <tino.calancha@gmail.com>,
24977@debbugs.gnu.org
Subject: bug#24977: 25.1; search and query-replace in Dired
Date: Mon, 21 Nov 2016 20:42:14 +0200 [thread overview]
Message-ID: <8490c105-416f-efef-ebc4-0e1cece68b42@yandex.ru> (raw)
In-Reply-To: <58aaafd8-4d69-452f-8afe-1cba7b3bc2f8@default>
On 21.11.2016 20:37, Drew Adams wrote:
> This is a major reason for this bug report (and bug #23428).
> The replacement is strictly less powerful. It is essentially
> just a `grep' or `find'. (And it depends on an outside program.)
It might be less powerful. On the flip side, the replacement is usually
faster. Especially in the "many files, few matches" situations.
>> Those should be doable, as long as the regexp contains at least
>> _something_ else.
>
> What does that mean? Specify what you mean by "_something_ else".
> Clearly you do NOT mean to support the regexps that Emacs supports.
For instance, if the regexp contains a simple literal and an Emacs-only
construct, we can remove the latter before passing the regexp to
find+grep, and then post-process the results inside Emacs using the full
syntax.
next prev parent reply other threads:[~2016-11-21 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 1:54 bug#24977: 25.1; search and query-replace in Dired Drew Adams
2016-11-21 2:13 ` Drew Adams
2016-11-21 14:07 ` Tino Calancha
2016-11-21 16:47 ` Dmitry Gutov
2016-11-21 17:41 ` Drew Adams
2016-11-21 18:17 ` Dmitry Gutov
2016-11-21 18:37 ` Drew Adams
2016-11-21 18:42 ` Dmitry Gutov [this message]
2016-11-21 18:51 ` Drew Adams
2016-11-21 19:50 ` Dmitry Gutov
2016-11-21 21:10 ` Drew Adams
2016-11-21 16:24 ` Eli Zaretskii
[not found] <<d27abfa8-adc7-4e5f-ab6e-c1b0824e50a0@default>
[not found] ` <<83h97094yh.fsf@gnu.org>
2016-11-21 16:36 ` Drew Adams
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=8490c105-416f-efef-ebc4-0e1cece68b42@yandex.ru \
--to=dgutov@yandex.ru \
--cc=24977@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=tino.calancha@gmail.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 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).