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:47:45 +0300 Message-ID: <83d29x96v2.fsf@gnu.org> References: <54193A70.9020901@member.fsf.org> <87wq8pwjen.fsf@uwakimon.sk.tsukuba.ac.jp> <837g0ptnlj.fsf@gnu.org> <87r3yxwdr6.fsf@uwakimon.sk.tsukuba.ac.jp> <87tx3tmi3t.fsf@fencepost.gnu.org> <834mvttgsf.fsf@gnu.org> <87lhp5m99w.fsf@fencepost.gnu.org> <87h9ztm5oa.fsf@fencepost.gnu.org> <87d2ahm3nw.fsf@fencepost.gnu.org> <871tqneyvl.fsf@netris.org> <87d2a54t1m.fsf@yeeloong.lan> <83lhotme1e.fsf@gnu.org> <871tql17uw.fsf@yeeloong.lan> <838uktm9gw.fsf@gnu.org> <87h9zgarvp.fsf@fencepost.gnu.org> <83y4srjaot.fsf@gnu.org> <83r3yhiu8c.fsf@gnu.org> <83siiw9c6t.fsf@gnu.org> <83zjd3846e.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1413092904 30816 80.91.229.3 (12 Oct 2014 05:48:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Oct 2014 05:48:24 +0000 (UTC) Cc: dak@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:48:16 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 1XdC0t-0007E3-3S for ged-emacs-devel@m.gmane.org; Sun, 12 Oct 2014 07:48:15 +0200 Original-Received: from localhost ([::1]:56185 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC0s-0004NH-Ma for ged-emacs-devel@m.gmane.org; Sun, 12 Oct 2014 01:48:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55874) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC0l-0004Mx-2l for emacs-devel@gnu.org; Sun, 12 Oct 2014 01:48:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdC0g-0002cq-L2 for emacs-devel@gnu.org; Sun, 12 Oct 2014 01:48:07 -0400 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:39240) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdC0a-0002Tv-1G; Sun, 12 Oct 2014 01:47:56 -0400 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NDB00I00GT5T700@mtaout25.012.net.il>; Sun, 12 Oct 2014 08:43:09 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NDB00CRAH7X4P70@mtaout25.012.net.il>; Sun, 12 Oct 2014 08:43:09 +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.181 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:175276 Archived-At: > Date: Sat, 11 Oct 2014 23:24:03 -0400 > From: Richard Stallman > CC: dak@gnu.org, mhw@netris.org, dmantipov@yandex.ru, > emacs-devel@gnu.org, handa@gnu.org, monnier@iro.umontreal.ca, > stephen@xemacs.org > > > No, it's just a matter of setting some parameter to specify a particular > > decision in decoding or encoding behavior. > > Specify, and then drag it all the way down the encoding/decoding > machinery. > > Could you be more concrete about the problem you are talking about here? The need to know about the semantics of this parameter all the way through the multi-layered hierarchy of our encoding/decoding implementation. > > It will be easy to specify one or the other, so why not make the default > > be strict, except in the primitives that operate on files? > > Because I believe this will annoy users and cause a lot of > complaining. > > Would you please describe a concrete scenario in which this might > annoy users? I already did, at least twice. I have no more scenarios to contribute, sorry. > Assume that any operation which decodes text _for a user to see_ > will specify flexible decoding. That means almost all of them, more-or-less. So it goes against what AFAIU Mark had in mind with "struct UTF-8".