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: Sat, 2 Oct 2010 22:40:15 +0200 Message-ID: References: <87bp7d1o6k.fsf@catnip.gol.com> <83bp7dqcgu.fsf@gnu.org> <87mxqw28cv.fsf@tux.homenetwork> <87mxqw4oup.fsf@tux.homenetwork> <83ocbcpqif.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 1286052049 914 80.91.229.12 (2 Oct 2010 20:40:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 2 Oct 2010 20:40:49 +0000 (UTC) Cc: Eli Zaretskii , Thierry Volpiatto , emacs-devel@gnu.org To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 02 22:40:46 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 1P28sw-0001hw-4n for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 22:40:46 +0200 Original-Received: from localhost ([127.0.0.1]:49833 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P28sv-0005om-Ie for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 16:40:45 -0400 Original-Received: from [140.186.70.92] (port=60680 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P28sp-0005oQ-9A for emacs-devel@gnu.org; Sat, 02 Oct 2010 16:40:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P28so-0007q8-16 for emacs-devel@gnu.org; Sat, 02 Oct 2010 16:40:39 -0400 Original-Received: from mail-iw0-f169.google.com ([209.85.214.169]:54095) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P28sn-0007pz-N2; Sat, 02 Oct 2010 16:40:37 -0400 Original-Received: by iwn33 with SMTP id 33so8120623iwn.0 for ; Sat, 02 Oct 2010 13:40: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=pKvITu+MPmxdtZKebxYPQPPnuN5iGTMc6yiSuCU1syU=; b=kHughKmkpfY8fBCie1EtK/6i7FS8TaFHvE3jf2oVm6w2Frl2KRZCN0t0FINxhTIre6 OmC7Z0LC8MjV9K8z7LvevFyXxuiBtkJ50uC/j34xz/G5xfpuyEfqLPu55MP4OleSng5w wHsm0x5cGRWZ0qp47TMAl68brlaUXzJA0jBMI= 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=sQxvnifgC4pWvms+UCWVRzucoguNKR5onm+s7TB0SysIEcn/vSviHq/ZdYg+iXxR4/ VS3F9lkFrMHbddZAmvVWkrnOSVT+/Abgk5kRV9+t17yWwf5A7n43jjver2sBnua2cBL8 H9CtnZD+ABaZbHaqJW/SPm2KJht1kzqIH8a48= Original-Received: by 10.231.166.9 with SMTP id k9mr7694803iby.127.1286052035929; Sat, 02 Oct 2010 13:40:35 -0700 (PDT) Original-Received: by 10.231.170.133 with HTTP; Sat, 2 Oct 2010 13:40:15 -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:131258 Archived-At: If Windows' built-in find command supports UTF-16, then that might be an option (maybe better since I think find will be installed on more Windows PCs) too: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/find.mspx?mfr=true It sounds like it does at least parts of what grep does. Try it out and see. /Mathias On Sat, Oct 2, 2010 at 5:56 PM, Lennart Borgman wrote: > On Sat, Oct 2, 2010 at 5:23 PM, Eli Zaretskii wrote: >>> From: Thierry Volpiatto >>> Date: Sat, 02 Oct 2010 17:05:18 +0200 >>> Cc: emacs-devel@gnu.org >>> >>> > Based on your advice I just took the trouble to install powershell. I >>> > can not see that it addresses the problem with utf-16, but maybe I am >>> > missing something. Can you please tell me how to search also utf-16 >>> > files with it? >>> >>> That's just an idea i sent, i personally don't use (or really few >>> sometimes on other machines) windows systems and i have just a basic >>> knowledge of all that is related to it and microsoft in general (e.g Powershell). >>> So i can't help you much here. >>> Anyway, Eli seem to have tried it and is not convinced. >> >> Looks like the PowerShell cmdlet that's supposed to be equivalent of >> Grep is Select-String. > > Yes, thanks. And that actually works with utf-16. > > So now we have a strange situation. > >