From: Lennart Borgman <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: What does Emacs on w32 know that grep can't figure out?
Date: Fri, 1 Oct 2010 17:03:49 +0200 [thread overview]
Message-ID: <AANLkTimU7BhEq15xDyrYRFPio2aZt3m10xOcOkXF2=Cg@mail.gmail.com> (raw)
In-Reply-To: <83ocbeqfx2.fsf@gnu.org>
On Fri, Oct 1, 2010 at 2:02 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Lennart Borgman <lennart.borgman@gmail.com>
>> Date: Fri, 1 Oct 2010 11:28:49 +0200
>> Cc: lekktu@gmail.com, emacs-devel@gnu.org
>>
>> > What's wrong with "M-x occur" and/or "M-x multi-occur"?
>>
>> They does not do what grep does.
>
> Like what?
Look at all the files in a directory.
>> And as I said opening the files in a buffer will be bad because of performance.
>
> What do you think Grep does? Doesn't it open the files and read them?
I think we have discussed before that putting the files in a buffer
would be a performance problem in a case like this, especially if the
file is big.
So I think something inside Emacs that could determine file coding but
did not put the file in a buffer is what I would want for this. Is
that hard to implement from what we have?
>> However using the internal regexp engine for searching the files would
>> be useful, but I have no idea how complicated it is to implement
>> something like that.
>
> Emacs does similar things in quite a few places already.
You mean similar to what I suggested above? (Or do you mean something
quite different, something on the elisp level?)
next prev parent reply other threads:[~2010-10-01 15:03 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 23:13 What does Emacs on w32 know that grep can't figure out? Lennart Borgman
2010-09-30 23:58 ` Juanma Barranquero
2010-10-01 0:29 ` Lennart Borgman
2010-10-01 0:37 ` Juanma Barranquero
2010-10-01 1:06 ` Lennart Borgman
2010-10-01 1:20 ` Juanma Barranquero
2010-10-01 1:32 ` Lennart Borgman
2010-10-01 1:49 ` Juanma Barranquero
2010-10-01 2:41 ` PJ Weisberg
2010-10-01 5:43 ` PJ Weisberg
2010-10-01 5:37 ` Jan D.
2010-10-01 7:34 ` Eli Zaretskii
2010-10-01 8:12 ` Andreas Schwab
2010-10-01 12:00 ` Eli Zaretskii
2010-10-01 12:40 ` Andreas Schwab
2010-10-01 17:19 ` Jan Djärv
2010-10-01 22:45 ` Stefan Monnier
2010-10-01 7:13 ` Eli Zaretskii
2010-10-01 9:28 ` Lennart Borgman
2010-10-01 10:35 ` Mathias Dahl
2010-10-01 11:24 ` Thierry Volpiatto
2010-10-01 11:26 ` Lennart Borgman
2010-10-01 12:02 ` Eli Zaretskii
2010-10-01 15:03 ` Lennart Borgman [this message]
2010-10-01 15:11 ` PJ Weisberg
2010-10-01 22:40 ` Stefan Monnier
2010-10-01 23:35 ` Miles Bader
2010-10-02 0:33 ` Lennart Borgman
2010-10-02 7:29 ` Eli Zaretskii
2010-10-02 10:12 ` Lennart Borgman
2010-10-02 10:32 ` Thierry Volpiatto
2010-10-02 10:50 ` Lennart Borgman
2010-10-02 12:01 ` Eli Zaretskii
2010-10-02 14:51 ` Lennart Borgman
2010-10-02 15:05 ` Thierry Volpiatto
2010-10-02 15:23 ` Eli Zaretskii
2010-10-02 15:56 ` Lennart Borgman
2010-10-02 20:40 ` Mathias Dahl
2010-10-02 22:20 ` Eli Zaretskii
2010-10-03 0:35 ` David Robinow
2010-10-03 4:05 ` Eli Zaretskii
2010-10-03 4:29 ` David Robinow
2010-10-03 5:39 ` Eli Zaretskii
2010-10-03 7:25 ` Thierry Volpiatto
2010-10-03 4:10 ` Lennart Borgman
2010-10-03 10:39 ` Thierry Volpiatto
2010-10-03 13:23 ` Thierry Volpiatto
2010-10-03 19:09 ` Eli Zaretskii
2010-10-03 22:50 ` Lennart Borgman
2010-10-05 0:46 ` Lennart Borgman
2010-10-05 0:51 ` Lennart Borgman
2010-10-05 0:56 ` Juanma Barranquero
2010-10-05 1:36 ` Lennart Borgman
2010-10-05 1:37 ` Lennart Borgman
2010-10-05 1:54 ` Juanma Barranquero
2010-10-02 11:59 ` Eli Zaretskii
2010-10-02 12:44 ` Lennart Borgman
2010-10-02 13:15 ` Eli Zaretskii
2010-10-01 7:09 ` Eli Zaretskii
2010-10-01 4:00 ` Stephen J. Turnbull
2010-10-01 7:03 ` Eli Zaretskii
2010-10-01 7:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimU7BhEq15xDyrYRFPio2aZt3m10xOcOkXF2=Cg@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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 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.