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: Wed, 15 Oct 2014 17:32:45 +0300 Message-ID: <837g015roy.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> <83bnph96kh.fsf@gnu.org> <83zjd07ce0.fsf@gnu.org> <834mv76udz.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1413383597 16206 80.91.229.3 (15 Oct 2014 14:33:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2014 14:33:17 +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 Wed Oct 15 16:33:09 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 1XePdS-0003rm-Dd for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 16:33:06 +0200 Original-Received: from localhost ([::1]:45051 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XePdS-00084C-1A for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 10:33:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XePdL-00083s-7F for emacs-devel@gnu.org; Wed, 15 Oct 2014 10:33:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XePdG-0006bh-Qr for emacs-devel@gnu.org; Wed, 15 Oct 2014 10:32:59 -0400 Original-Received: from mtaout26.012.net.il ([80.179.55.182]:37138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XePdA-0006Rl-4Y; Wed, 15 Oct 2014 10:32:48 -0400 Original-Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0NDH00700P3J0V00@mtaout26.012.net.il>; Wed, 15 Oct 2014 17:31:02 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NDH0040SPNQYZ30@mtaout26.012.net.il>; Wed, 15 Oct 2014 17:31:02 +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.182 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:175410 Archived-At: > Date: Wed, 15 Oct 2014 09:16:20 -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 > > I believe the commands that use shell-command-to-string are a good > example of these cases. That function is frequently used as > infrastructure to query an external program about something, and the > result is then used, at least in some cases, to decide how to proceed. > > 1. The scenario we've been told about is where the invalid UTF-8 gets > passed on to some other program. I don't think any harm will come if > Emacs itself looks at the output of the command. Emacs does not > generally get confused by raw bytes. What Emacs gets from a program it can as easily send to another (or the same one). > 2. It would not be hard to make another function (which does strict > decoding) to recommend instead of shell-command-to-string for use in > Lisp code in certain cases. > > 3. It would be easy enough to make shell-command-to-string do flexible > decoding when called interactively and do strict decoding when called > noninteractively -- controlled through an optional argument. I envision complaints from users if we do that.