From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Sun, 12 Oct 2014 08:54:06 +0300 Message-ID: <83bnph96kh.fsf@gnu.org> References: <87d2ahm3nw.fsf@fencepost.gnu.org> <871tqneyvl.fsf@netris.org> <87zjd9swfj.fsf@uwakimon.sk.tsukuba.ac.jp> <87oatnqpml.fsf@uwakimon.sk.tsukuba.ac.jp> <874mvdrj45.fsf@uwakimon.sk.tsukuba.ac.jp> <20141009044917.GA19957@fencepost.gnu.org> <83lhopisfr.fsf@gnu.org> <87ppe1pldu.fsf@uwakimon.sk.tsukuba.ac.jp> <8761ft5wpo.fsf@fencepost.gnu.org> <83k349b0vj.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1413093295 2136 80.91.229.3 (12 Oct 2014 05:54:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Oct 2014 05:54:55 +0000 (UTC) Cc: dak@gnu.org, mikegerwitz@gnu.org, mhw@netris.org, dmantipov@yandex.ru, emacs-devel@gnu.org, handa@gnu.org, monnier@iro.umontreal.ca, stephen@xemacs.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 12 07:54:46 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XdC79-0000bO-2M for ged-emacs-devel@m.gmane.org; Sun, 12 Oct 2014 07:54:43 +0200 Original-Received: from localhost ([::1]:56207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC78-0005VF-Ig for ged-emacs-devel@m.gmane.org; Sun, 12 Oct 2014 01:54:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC6s-0005Ud-98 for emacs-devel@gnu.org; Sun, 12 Oct 2014 01:54:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdC6n-0004CB-SM for emacs-devel@gnu.org; Sun, 12 Oct 2014 01:54:26 -0400 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:58397) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC6i-0004Bf-VJ; Sun, 12 Oct 2014 01:54:17 -0400 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NDB00D00HEGEI00@mtaout28.012.net.il>; Sun, 12 Oct 2014 08:52:39 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NDB00AJAHNRVN30@mtaout28.012.net.il>; Sun, 12 Oct 2014 08:52:39 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:175277 Archived-At: > Date: Sat, 11 Oct 2014 23:24:30 -0400 > From: Richard Stallman > CC: dak@gnu.org, mikegerwitz@gnu.org, mhw@netris.org, > dmantipov@yandex.ru, emacs-devel@gnu.org, handa@gnu.org, > monnier@iro.umontreal.ca, stephen@xemacs.org > > What is an example of a protocol that doesn't specify an encoding? I'm not an expert, so I actually have trouble coming up with protocols that _do_ specify an encoding. Maybe someone else could help out. > And, of course, when you invoke a program locally, there's usually no > protocol at all involved. > > Likewise, we need to look at some real cases. Not sure what you mean by that. M-! and M-| is what I had in mind. > You can invoke any program with M-!; I think in that case heuristic > decoding is what users want. But that's about 99.99% of the uses. So perhaps we are in violent agreement after all. > When functions run call-process on specific, what decoding is really > right? I don't think there's a way to know that, except in a very few specific cases (like speller, for example). We currently use an encoding derived from the user locale, but that's a heuristics that has known limitations and known use cases where it simply fails (but no better guess is available).