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: Thu, 09 Oct 2014 20:37:20 +0300 Message-ID: <83k349b0vj.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> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1412876251 2613 80.91.229.3 (9 Oct 2014 17:37:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Oct 2014 17:37:31 +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 Thu Oct 09 19:37:23 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 1XcHeU-0008PN-I4 for ged-emacs-devel@m.gmane.org; Thu, 09 Oct 2014 19:37:22 +0200 Original-Received: from localhost ([::1]:44390 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcHeU-0002NL-4i for ged-emacs-devel@m.gmane.org; Thu, 09 Oct 2014 13:37:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46122) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcHeM-0002Mp-Kx for emacs-devel@gnu.org; Thu, 09 Oct 2014 13:37:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XcHeI-0007CD-7l for emacs-devel@gnu.org; Thu, 09 Oct 2014 13:37:14 -0400 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:43184) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcHeD-0007B2-DH; Thu, 09 Oct 2014 13:37:05 -0400 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0ND600300T763N00@mtaout24.012.net.il>; Thu, 09 Oct 2014 20:30:54 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0ND600K9PTZH7CA0@mtaout24.012.net.il>; Thu, 09 Oct 2014 20:30:54 +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.180 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:175194 Archived-At: > Date: Thu, 09 Oct 2014 13:23:43 -0400 > From: Richard Stallman > CC: stephen@xemacs.org, handa@gnu.org, mhw@netris.org, > dmantipov@yandex.ru, emacs-devel@gnu.org, mikegerwitz@gnu.org, > monnier@iro.umontreal.ca, eliz@gnu.org > > So first I let the locale and other mechanisms choose an encoding, then > try getting at its choice of coding system before any prompts appear, > then I convert the symbol to a string, check whether the string ends > with "-with-rawbytes" and append it if needed > > Is that really a likely scenario? It is what happens with all our general-purpose commands and APIs that invoke subprocesses, like shell-command, shell-command-on-region, start-process, etc. The default is to use the locale-specific encoding, and users, of course, are not required to type any specific coding systems when they invoke those commands/functions. > I expect that a program, doing some non-editing job involving a > network connection, ought to specify a fixed coding system in accord > with the protocol it is communicating with. The protocols rarely specify encoding, AFAIK. If they do, we do use them, e.g., when decoding an email message that specifies its MIME charset. But that comes _after_ we already have read the mail into a buffer in its raw undecoded form. And, of course, when you invoke a program locally, there's usually no protocol at all involved.