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: Sat, 2 Oct 2010 17:56:41 +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=UTF-8 X-Trace: dough.gmane.org 1286035034 1725 80.91.229.12 (2 Oct 2010 15:57:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 2 Oct 2010 15:57:14 +0000 (UTC) Cc: emacs-devel@gnu.org, Thierry Volpiatto To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 02 17:57:11 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 1P24SV-0006DZ-7j for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 17:57:11 +0200 Original-Received: from localhost ([127.0.0.1]:53149 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P24SU-000506-GW for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 11:57:10 -0400 Original-Received: from [140.186.70.92] (port=37798 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P24SP-0004zL-BS for emacs-devel@gnu.org; Sat, 02 Oct 2010 11:57:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P24SO-0007SN-7g for emacs-devel@gnu.org; Sat, 02 Oct 2010 11:57:05 -0400 Original-Received: from mail-qy0-f169.google.com ([209.85.216.169]:36411) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P24SO-0007SJ-53; Sat, 02 Oct 2010 11:57:04 -0400 Original-Received: by qyk32 with SMTP id 32so732922qyk.0 for ; Sat, 02 Oct 2010 08:57:03 -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=7qgeCWoDYoyEsj8Fm1y/py4vVsW1WugZbcCqvRHP4Oc=; b=rAE90sF2DW/ShKEW1cR6Z1rHqmVCb8Jo6HGabN8GVX2aJ6Y6NJvhZAPRP+eyzE8S0F 0TMbTmn+gWIw28Y9ckYFrA8aha+PRNoQY/vDgDgw76E6hHa4imWpywepSOwC9z+m0obt lm5sCfTn/jaN9Oc6BiABfo9neuKzevI4WwKBE= 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=rxC39kIVEc/YjChnhRiLNanIUWUhrIl0jxDSVmba2lsqYSS3qQj8S77hg84x2Ahc00 sC1jBtfakrBmm54uGTCKg1i0vOdHAf16UmyTbqelk9nNKNr7ovUYy0bc5q+P6uOiqQUt yHrjBcGryFyQZdCRQfOjVpbmmY4wVTzD8X2W8= Original-Received: by 10.229.240.79 with SMTP id kz15mr5118225qcb.200.1286035021673; Sat, 02 Oct 2010 08:57:01 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Sat, 2 Oct 2010 08:56:41 -0700 (PDT) In-Reply-To: <83ocbcpqif.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:131248 Archived-At: 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.