From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: What does Emacs on w32 know that grep can't figure out? Date: Fri, 1 Oct 2010 17:03:49 +0200 Message-ID: References: <83y6aiqtbq.fsf@gnu.org> <83ocbeqfx2.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1285945901 1063 80.91.229.12 (1 Oct 2010 15:11:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Oct 2010 15:11:41 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 01 17:11:40 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P1hGt-0003RK-7n for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 17:11:39 +0200 Original-Received: from localhost ([127.0.0.1]:39767 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1hGs-0008OX-Ce for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 11:11:38 -0400 Original-Received: from [140.186.70.92] (port=48095 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1hEV-0006d5-V7 for emacs-devel@gnu.org; Fri, 01 Oct 2010 11:09:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1h9h-0006lZ-3l for emacs-devel@gnu.org; Fri, 01 Oct 2010 11:04:14 -0400 Original-Received: from mail-qw0-f41.google.com ([209.85.216.41]:36074) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1h9h-0006lS-1a; Fri, 01 Oct 2010 11:04:13 -0400 Original-Received: by qwb8 with SMTP id 8so1377830qwb.0 for ; Fri, 01 Oct 2010 08:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ENzs5pBbVDeZKVJkOUgxlV4gCxHX/l+su0uZgXF3L9o=; b=xjjkvgITGZgzpYYDvf2JmdOOcQ478BRLEDeSpcnOtnz05bpnL4VvkuvfxENsX+2rJx VF9Wn+Ysn6iUfhqoLrMtbo2r0xESqE5gb4/5nlTLd3VCBtonUDts+wvfiBeWZD5Rrenf XY92JkucqON3j+4ejQvj6QwKgu/PIw3SIYoYw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=P0PXghLTZAb7K0o2GFBH9C9wiqxDagdCNwP1fa9CJ1XpS4BirhCADNFwOORFF0FmDN sehqdtJMUwyda1iYb/6pHVX9cjXA4KG2V7HiZBYYzCpmvSPch3T87lwA/aYgRWLR02MY dLhwJQIejp4xYVyz0DbHDofa109neBcsIw6xM= Original-Received: by 10.224.80.203 with SMTP id u11mr3717182qak.354.1285945452411; Fri, 01 Oct 2010 08:04:12 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Fri, 1 Oct 2010 08:03:49 -0700 (PDT) In-Reply-To: <83ocbeqfx2.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131163 Archived-At: On Fri, Oct 1, 2010 at 2:02 PM, Eli Zaretskii wrote: >> From: Lennart Borgman >> 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 perfo= rmance. > > What do you think Grep does? =C2=A0Doesn't it open the files and read the= m? 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?)