From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 23426@debbugs.gnu.org, dgutov@yandex.ru,
heinz@h-rommerskirchen.de, kaushal.modi@gmail.com
Subject: bug#23426: 25.0.93; dired-do-find-regexp doesn't find newline
Date: Wed, 4 May 2016 09:23:23 -0700 (PDT) [thread overview]
Message-ID: <7013d5db-f294-4866-bdf9-79b04cd8f8a1@default> (raw)
In-Reply-To: <<83lh3piyvq.fsf@gnu.org>>
> > I'm trying to be clear that I _welcome_ your feature,
> > based on the description. It sounds like something useful.
> >
> > I just don't think it's great that you feel you should
> > immediately replace other, existing ways to search,
> > including grabbing their key bindings.
>
> Maybe you should actually try it before talking about it.
I'm not talking about it. I'm talking about what it's replacing.
I can assume that it is wonderful. And I understand something
about the usefulness of users seeing a set of search hits
together and being able to filter and choose among them.
I don't, for even a moment, doubt its advantages.
None of that speaks to why it should replace, instead of be an
addition to, the longstanding `A' and `Q' behavior, which do
not let users see a set of search hits.
next parent reply other threads:[~2016-05-04 16:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] ` <<83oa8liz53.fsf@gnu.org>
2016-05-04 16:39 ` bug#23426: 25.0.93; dired-do-find-regexp doesn't find newline 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
2016-05-02 17:17 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
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
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=7013d5db-f294-4866-bdf9-79b04cd8f8a1@default \
--to=drew.adams@oracle.com \
--cc=23426@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=heinz@h-rommerskirchen.de \
--cc=kaushal.modi@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).