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: Tue, 5 Oct 2010 03:37:08 +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> <83d3rrozyw.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 1286242668 12710 80.91.229.12 (5 Oct 2010 01:37:48 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 5 Oct 2010 01:37:48 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org, thierry.volpiatto@gmail.com To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 05 03:37:43 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 1P2wTN-00022b-Ue for ged-emacs-devel@m.gmane.org; Tue, 05 Oct 2010 03:37:42 +0200 Original-Received: from localhost ([127.0.0.1]:35003 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2wTN-00050x-9d for ged-emacs-devel@m.gmane.org; Mon, 04 Oct 2010 21:37:41 -0400 Original-Received: from [140.186.70.92] (port=42617 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2wTF-00050F-AV for emacs-devel@gnu.org; Mon, 04 Oct 2010 21:37:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P2wTE-0007NM-7a for emacs-devel@gnu.org; Mon, 04 Oct 2010 21:37:33 -0400 Original-Received: from mail-qy0-f169.google.com ([209.85.216.169]:64217) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P2wTE-0007NC-1c; Mon, 04 Oct 2010 21:37:32 -0400 Original-Received: by qyk33 with SMTP id 33so2435297qyk.0 for ; Mon, 04 Oct 2010 18:37:31 -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=bSncEDIfX4+NFudG/+PiGh3PtOSf1r5wZOTGwmsyTaY=; b=Z45QuuSh/SnA0NQ43t1XPDX2U5u/QEau8DM7wl+a9w3dGbkWYeyxEK+nsQY4n/k1FM ta2TnAuk1FCQPsGTV/tkMtXNDfqYcnDdZZat4f/SJ4/cbiKHqEoGnjraSQMh9TY15mzU M4R6NyT/j48UpgbLQJXVQqvG75EX31mdcekOY= 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=iJZfIFy/xWHzB1ejTbAi7AMRbOa3YW/BOlnRVXoFx2y+l2AX3JIz2IQEeMOzxaChZt 5Z7SxEiKbffkxtqOxitqem9ZNVO9kjqtC2P/qUw5EnxijbhlUcKwogbQc047HjCht/gF yHfPZsoht9aqAd/0V0akY/51b6kreY5lXsLv4= Original-Received: by 10.229.2.28 with SMTP id 28mr7563045qch.267.1286242649119; Mon, 04 Oct 2010 18:37:29 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Mon, 4 Oct 2010 18:37:08 -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:131342 Archived-At: On Tue, Oct 5, 2010 at 3:36 AM, Lennart Borgman wrote: > On Tue, Oct 5, 2010 at 2:56 AM, Juanma Barranquero wrote: >> >>> What can we do? The options I can see are: >> >> C.- Do nothing, and leave to the user the task of finding a tool that >> can grep utf-16. >> >> D.- Do nothing, and leave to the user the task of converting the >> utf-16 files to another coding, as utf-16 is the internal format of >> 32-bit Windows APIs, but it is rarely found in files, even on Windows. > > How would the user no which of C and D we have choosen? no => know ... > If we decide on this (which seems likely now), then should we not > change default file coding system to utf-8? We kind of expect that, > but I do not understand what consequences changing the default file > coding system will have. >