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 16:51:20 +0200 Message-ID: References: <87bp7d1o6k.fsf@catnip.gol.com> <83bp7dqcgu.fsf@gnu.org> <87mxqw28cv.fsf@tux.homenetwork> 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 1286031111 19204 80.91.229.12 (2 Oct 2010 14:51:51 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 2 Oct 2010 14:51:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 02 16:51:50 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 1P23RF-0007Vk-PN for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 16:51:50 +0200 Original-Received: from localhost ([127.0.0.1]:43806 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P23RF-0001q0-A6 for ged-emacs-devel@m.gmane.org; Sat, 02 Oct 2010 10:51:49 -0400 Original-Received: from [140.186.70.92] (port=36285 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P23R8-0001om-O4 for emacs-devel@gnu.org; Sat, 02 Oct 2010 10:51:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P23R7-00056G-E3 for emacs-devel@gnu.org; Sat, 02 Oct 2010 10:51:42 -0400 Original-Received: from mail-qy0-f176.google.com ([209.85.216.176]:55273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P23R7-000567-8o for emacs-devel@gnu.org; Sat, 02 Oct 2010 10:51:41 -0400 Original-Received: by qyk36 with SMTP id 36so5357827qyk.0 for ; Sat, 02 Oct 2010 07:51:40 -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=z8nQcQw8fk7TS49x6L+2bvjxiW19fD7yY5BEDq2j0K8=; b=OUdP78/PFzpfq+AnuylZB1AVRs5E5gpNJ0dRZUBYiIfAni6AtJdOj3txk/5mksKL9c GtCxyZI7oSUGSaf1XA+4g0YAJ7ch5QHDDGMK1rTiNcwljtJL2c4o30pTHGKfddvsBQbk KurLOQNmYEAI+qOcKErXYz1YUtwaRRDilRmtE= 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=gpjEhiqmu3FYozUy737iM5ty4VDfaoTMEqsPpylmg/QK0FHiiQyBiW8R27GIwwiW54 G17hc1BVOfMmIHG2/WHLJJ+mJUexC4SO+oBrRsBGtZBjANQlOmzIbWvBtmUTzAiePZ+d 9I2cE/7T74JB1nrzp62ycWBylBzYU7yQFHy9M= Original-Received: by 10.229.218.69 with SMTP id hp5mr5169384qcb.18.1286031100554; Sat, 02 Oct 2010 07:51:40 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Sat, 2 Oct 2010 07:51:20 -0700 (PDT) In-Reply-To: <87mxqw28cv.fsf@tux.homenetwork> 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:131242 Archived-At: On Sat, Oct 2, 2010 at 12:32 PM, Thierry Volpiatto wrote: > Lennart Borgman writes: > >> On Sat, Oct 2, 2010 at 9:29 AM, Eli Zaretskii wrote: >>>> From: Lennart Borgman >>>> Date: Sat, 2 Oct 2010 02:33:32 +0200 >>>> Cc: emacs-devel@gnu.org >>>> >>>> So where is the problem? Is utf-16 actually used on w32 in many apps? >>>> Or is this a left-over in CCleaner? >>> >>> UTF-16 is used for all the Unicode APIs on Windows. =C2=A0That's the >>> implementation of the wchar_t type on Windows. =C2=A0In particular, all= the >>> file names in the NTFS filesystem are actually stored as UTF-16, and >>> all the OS databases in memory are stored in UTF-16 format. >>> >>> So this is not a left-over, this is what Windows uses internally. >> >> >> Thanks. So then the question is why the grep program does not support >> it. Is this a policy question, a lack of resources, or something else? >> >> > It seem most modern windows versions come with powershell. > Why windows users don't use it as backend for Emacs instead of using > external Gnuwin32 programs? 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?