From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Glenn Morris <rgm@gnu.org>
Cc: 23426-done@debbugs.gnu.org, heinz@h-rommerskirchen.de
Subject: bug#23426: 25.0.93; dired-do-find-regexp doesn't find newline
Date: Wed, 4 May 2016 02:08:36 +0300 [thread overview]
Message-ID: <0e97c691-b726-7002-30d7-d5da074d6cac@yandex.ru> (raw)
In-Reply-To: <837ffbktdt.fsf@gnu.org>
Version: 25.1
On 05/03/2016 07:18 PM, Eli Zaretskii wrote:
>> (The fact that it uses grep should perhaps be documented, since it
>> affects what one can search for.)
>
> I added that to the doc string. I'm much less inclined to state this
> ion the manual, as this seems to be a subtle implementation detail,
> and is probably subject to change.
Right, and it's not easy to describe, because for now we support only
constructs that Grep understands but require the user to escape the
terms the way Emacs requires, not Grep (so the result is somewhere
between BRE and ERE).
Hopefully, we'll allow more Emacs-specific terms in the future (by
stripping them out before giving the regexp to Grep, and then verifying
the matches in Emacs with the correct regexp).
>> For this specific example, a grep-ish way to find empty lines is '^$'.
>> However, using "A" to search for that (or the empty regexp) causes Emacs
>> to hang indefinitely. :(
>
> That's a bug that should be fixed, for sure.
Fixed in 4d8fd9c. Closing.
next prev parent reply other threads:[~2016-05-03 23:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 17:17 bug#23426: 25.0.93; dired-do-find-regexp doesn't find newline Heinz Rommerskirchen
2016-05-02 17:41 ` Drew Adams
2016-05-02 17:45 ` Drew Adams
2016-05-02 18:23 ` Dmitry Gutov
2016-05-03 1:18 ` Glenn Morris
2016-05-03 16:18 ` Eli Zaretskii
2016-05-03 23:08 ` Dmitry Gutov [this message]
2016-05-03 17:22 ` Dmitry Gutov
2016-05-03 19:00 ` Glenn Morris
2016-05-03 20:59 ` Dmitry Gutov
2016-05-04 2:05 ` Drew Adams
2016-05-04 2:34 ` Dmitry Gutov
2016-05-04 4:24 ` Drew Adams
2016-05-04 15:01 ` Eli Zaretskii
[not found] ` <<838tzpkgtj.fsf@gnu.org>
2016-05-04 15:31 ` Drew Adams
2016-05-04 15:39 ` Dmitry Gutov
2016-05-04 16:04 ` Drew Adams
2016-05-04 16:13 ` Eli Zaretskii
2016-05-04 16:00 ` Eli Zaretskii
[not found] ` <<83r3dhizis.fsf@gnu.org>
2016-05-04 16:32 ` Drew Adams
2016-05-04 16:51 ` Eli Zaretskii
2016-05-04 5:00 ` Kaushal Modi
2016-05-04 10:32 ` Dmitry Gutov
2016-05-04 13:32 ` Drew Adams
2016-05-04 13:49 ` Dmitry Gutov
2016-05-04 15:31 ` Drew Adams
2016-05-04 16:01 ` Eli Zaretskii
2016-05-04 15:15 ` Eli Zaretskii
2016-05-04 15:10 ` Eli Zaretskii
[not found] ` <<6a4860bb-2b39-4da4-b2a7-7b8d15211fee@default>
[not found] ` <<831t5hkg6x.fsf@gnu.org>
2016-05-04 15:39 ` Drew Adams
2016-05-04 15:53 ` Dmitry Gutov
2016-05-04 16:10 ` Drew Adams
2016-05-04 16:14 ` Eli Zaretskii
2016-05-04 16:20 ` Kaushal Modi
2016-05-04 16:25 ` Dmitry Gutov
2016-05-04 16:41 ` Eli Zaretskii
2016-05-04 18:06 ` Kaushal Modi
2016-05-04 16:28 ` Dmitry Gutov
2016-05-04 16:08 ` Eli Zaretskii
[not found] <<<CAFyQvY0KYfeg9-f8DiCJcEy5-W=yRFykLLpCHRtCeqzz9Bdi0g@mail.gmail.com>
[not found] ` <<3ba077a2-21e0-9799-4f8b-c07bd1623853@yandex.ru>
[not found] ` <<<6a4860bb-2b39-4da4-b2a7-7b8d15211fee@default>
[not found] ` <<<831t5hkg6x.fsf@gnu.org>
[not found] ` <<7da95e19-50ff-4ca5-a5b8-2a7f65c2a7cd@default>
[not found] ` <<6cf9e2bf-fa90-3783-b30a-9021074790b0@yandex.ru>
[not found] ` <<93badbbc-31f6-409d-8dff-d67e9202deca@default>
[not found] ` <<83lh3piyvq.fsf@gnu.org>
2016-05-04 16:23 ` Drew Adams
[not found] ` <<83oa8liz53.fsf@gnu.org>
2016-05-04 16:39 ` Drew Adams
2016-05-04 18:20 ` John Wiegley
2016-05-04 20:09 ` Drew Adams
2016-05-04 21:13 ` John Wiegley
2016-05-05 17:07 ` Eli Zaretskii
2016-05-05 23:44 ` John Wiegley
2016-05-05 17:03 ` Eli Zaretskii
2016-05-05 17:01 ` Eli Zaretskii
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=0e97c691-b726-7002-30d7-d5da074d6cac@yandex.ru \
--to=dgutov@yandex.ru \
--cc=23426-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heinz@h-rommerskirchen.de \
--cc=rgm@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).