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: Sun, 3 Oct 2010 06:10:14 +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 1286079880 21110 80.91.229.12 (3 Oct 2010 04:24:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 3 Oct 2010 04:24:40 +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 Sun Oct 03 06:24:38 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 1P2G7p-0004PQ-Tv for ged-emacs-devel@m.gmane.org; Sun, 03 Oct 2010 06:24:38 +0200 Original-Received: from localhost ([127.0.0.1]:57046 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2G7p-00047F-7y for ged-emacs-devel@m.gmane.org; Sun, 03 Oct 2010 00:24:37 -0400 Original-Received: from [140.186.70.92] (port=48998 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2G6P-0003LO-GC for emacs-devel@gnu.org; Sun, 03 Oct 2010 00:23:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P2FuF-0005w6-F3 for emacs-devel@gnu.org; Sun, 03 Oct 2010 00:10:36 -0400 Original-Received: from mail-qy0-f176.google.com ([209.85.216.176]:40375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P2FuF-0005w2-Cw; Sun, 03 Oct 2010 00:10:35 -0400 Original-Received: by qyk36 with SMTP id 36so6001961qyk.0 for ; Sat, 02 Oct 2010 21:10:34 -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=xVpguUWXZeUYnN+mhqPDuwTqUleMIi8MmKWVi7BARXQ=; b=wCgRnKAlENmM6oJaFZQdxguoUvLA6eKzGnc7U1MaXUxa760y2+kUUyx9L5iPk2pxbJ Q/gg4DdbZQoO0FahIXuBFaPwW7BBHZ88u9lvvXU/j3Ky1/sU7OYqtJ5wIkoYseZajRpT qDck6vU9lMoSQx/1DnIS9AoN1b+oZ2Tv5/0Do= 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=CMYs1jYFS6eomXQSHCb5u5EhNzJY7GQVdNLYks0PjO+oTOdobrv10yCDjLU5Assx6G KhNji7zsmBdR6eN20ZggjGhT76y7r6e6V07RxkXKRzZKibWOOEtwLpKGkrOunLyJilcf Yi3zsMiKhALP3a45Lthg3xFHnTbh3W+NHiWz8= Original-Received: by 10.229.236.74 with SMTP id kj10mr5496178qcb.221.1286079034118; Sat, 02 Oct 2010 21:10:34 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Sat, 2 Oct 2010 21:10: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:131274 Archived-At: 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. Or maybe not. Looking at the documentation for Select-String here http://technet.microsoft.com/en-us/library/dd315403.aspx it does not look as it autodetects the coding system in the file. It does not even say it can handle utf-16, or at least I can't find it. Maybe someone who understands this better can see it there?