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: Mon, 4 Oct 2010 00:50:02 +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 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1286146951 24069 80.91.229.12 (3 Oct 2010 23:02:31 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 3 Oct 2010 23:02:31 +0000 (UTC) Cc: thierry.volpiatto@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 04 01:02:30 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 1P2XZd-0006Fq-QC for ged-emacs-devel@m.gmane.org; Mon, 04 Oct 2010 01:02:30 +0200 Original-Received: from localhost ([127.0.0.1]:44502 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2XZd-00012P-Gg for ged-emacs-devel@m.gmane.org; Sun, 03 Oct 2010 19:02:29 -0400 Original-Received: from [140.186.70.92] (port=37367 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P2XYE-000057-2t for emacs-devel@gnu.org; Sun, 03 Oct 2010 19:01:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P2XNw-00056R-TD for emacs-devel@gnu.org; Sun, 03 Oct 2010 18:50:26 -0400 Original-Received: from mail-qw0-f41.google.com ([209.85.216.41]:36234) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P2XNw-00056E-Lk; Sun, 03 Oct 2010 18:50:24 -0400 Original-Received: by qwb8 with SMTP id 8so3014518qwb.0 for ; Sun, 03 Oct 2010 15:50:24 -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=jOLh0o8KvG6iXb9qhcDD2NYvcmp1COIOEvdTVXWj8PY=; b=j7P2t0P97hTUO1nTqW3AEYA3qKMzcQrSDFppclmsTpVGkz/bLrgZl4EiiGuJkKxut5 +cFk6yQZVAWDcsoNtUO+k3nlZzqgGkSNSd1l4qNV50UJnie23Ur3EpQEmJxzoZktv5Ag 4weE1Mx8C8lGqATe5MygFED9LQXvkdq+6Yus0= 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=d9u/8cVoUbvNL9+u4WxNoJoKQlB7RU1rV2rsv+Vw+lgTlX+MmVjAnnOFZadlYmzd3k pW9JEQQws4SgWbjP0AQPUEaBRnx/OBpLpsOWyRVA8NQejbyJyyAHJ0TAtmSnewulyXvb slsoa4VnI0TojMFWqmMZray8dGYi/p7jdWnWo= Original-Received: by 10.229.182.84 with SMTP id cb20mr6264361qcb.126.1286146223032; Sun, 03 Oct 2010 15:50:23 -0700 (PDT) Original-Received: by 10.229.220.195 with HTTP; Sun, 3 Oct 2010 15:50:02 -0700 (PDT) In-Reply-To: <83d3rrozyw.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:131302 Archived-At: On Sun, Oct 3, 2010 at 9:09 PM, Eli Zaretskii wrote: >> From: Lennart Borgman >> Date: Sun, 3 Oct 2010 06:10:14 +0200 >> Cc: Thierry Volpiatto , emacs-devel@gnu.org >> >> =C2=A0 http://technet.microsoft.com/en-us/library/dd315403.aspx >> >> it does not look as it autodetects the coding system in the file. > > Why should it? I don't understand why you are asking. The answer is of course: Because it would be useful when searching for words in many files (and you do not know their coding system). Or, don't you think so? > What tool does, besides Emacs? I am not sure, but I would expect at least some better search engines/indexers to do this. I can't see how they can avoid it. >> It does not even say it can handle utf-16, or at least I can't find >> it. > > It does support UTF-16. =C2=A0That's the "Unicode" part of the values you > can submit to the -Encoding option (you need to "think MS" to get it). Thanks.