From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mathias Dahl Newsgroups: gmane.emacs.devel Subject: Re: What does Emacs on w32 know that grep can't figure out? Date: Fri, 1 Oct 2010 12:35:14 +0200 Message-ID: References: <83y6aiqtbq.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1285929353 18256 80.91.229.12 (1 Oct 2010 10:35:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Oct 2010 10:35:53 +0000 (UTC) Cc: lekktu@gmail.com, Eli Zaretskii , emacs-devel@gnu.org To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 01 12:35:49 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 1P1cxv-0004L2-DO for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 12:35:47 +0200 Original-Received: from localhost ([127.0.0.1]:46387 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1cxu-0004EM-UT for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 06:35:46 -0400 Original-Received: from [140.186.70.92] (port=50446 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1cxo-0004DU-Qt for emacs-devel@gnu.org; Fri, 01 Oct 2010 06:35:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1cxl-0004eq-Mk for emacs-devel@gnu.org; Fri, 01 Oct 2010 06:35:40 -0400 Original-Received: from mail-iw0-f169.google.com ([209.85.214.169]:51448) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1cxl-0004dq-FW; Fri, 01 Oct 2010 06:35:37 -0400 Original-Received: by iwn33 with SMTP id 33so5670999iwn.0 for ; Fri, 01 Oct 2010 03:35:36 -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; bh=uz4fR8zaNfJp7YvNJQ6CNZOz+Nm+XPw7sytj+31pZDw=; b=RfgguC+QhzTy+MS7WvCPOlBB1C6e7K3kJjKi+vR7bVz0Gnz0lGgVOHqTOhr3Lg2JuB 43+nImJIYPtJwqiDgd2vM6EcR/88NG1Oy3Otqe+zhb4yuKZLcOG5AMmvt/8oqnVTfkTb q9uwfYMyjdQ5v/g3w+DgWmNQBPqrt5/7WFHCk= 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; b=QKU8Uo4QbCD5nkxWtOkwJY+MSQnFcpw3tG7wZudouKAmEyUnYo9lqVUXIgAliShlzw 8iPmvH5UCNY2M35cp0MVX6qywi9sBpHio4Bgg5qxI+8uKduiawPfL/+FmJ0+QtgBAunv xLardZCbkNoUJebXjr1QwhGzl0Ky+KaV95q9c= Original-Received: by 10.231.19.74 with SMTP id z10mr5418029iba.120.1285929335913; Fri, 01 Oct 2010 03:35:35 -0700 (PDT) Original-Received: by 10.231.170.133 with HTTP; Fri, 1 Oct 2010 03:35:14 -0700 (PDT) In-Reply-To: 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:131142 Archived-At: I often use `% g' in Dired for finding files with a certain text in them. Together with recursive Dired listings this often solves my needs (although it is slower than using grep.) /Mathias On Fri, Oct 1, 2010 at 11:28 AM, Lennart Borgman wrote: > On Fri, Oct 1, 2010 at 9:13 AM, Eli Zaretskii wrote: >>> From: Lennart Borgman >>> Date: Fri, 1 Oct 2010 02:29:35 +0200 >>> Cc: Emacs-Devel devel >>> >>> > How do we handle what? If you mean, how can Emacs read the text just >>> > fine... Emacs has supported UTF-16 and many other coding systems for >>> > years. >>> >>> Using grep is an integral part of Emacs. If grep does not support the >>> coding then that part of Emacs will fail. >> >> What's wrong with "M-x occur" and/or "M-x multi-occur"? > > They does not do what grep does. > > And as I said opening the files in a buffer will be bad because of performance. > > 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. > >