From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark H Weaver Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Sun, 12 Oct 2014 22:40:51 -0400 Message-ID: <8761foy9n0.fsf@netris.org> References: <54193A70.9020901@member.fsf.org> <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> <8738auyxke.fsf@netris.org> <874mvaoys7.fsf@uwakimon.sk.tsukuba.ac.jp> <87h9z91y52.fsf@fencepost.gnu.org> <871tqdpjoi.fsf@uwakimon.sk.tsukuba.ac.jp> <874mv91n6a.fsf@fencepost.gnu.org> <87zjd1ny1h.fsf@uwakimon.sk.tsukuba.ac.jp> <87zjd1z0yl.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413168088 13490 80.91.229.3 (13 Oct 2014 02:41:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Oct 2014 02:41:28 +0000 (UTC) Cc: "Stephen J. Turnbull" , emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 13 04:41:18 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 1XdVZV-0004UR-NZ for ged-emacs-devel@m.gmane.org; Mon, 13 Oct 2014 04:41:17 +0200 Original-Received: from localhost ([::1]:59906 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdVZV-0007cD-2E for ged-emacs-devel@m.gmane.org; Sun, 12 Oct 2014 22:41:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdVZE-0007bx-0O for emacs-devel@gnu.org; Sun, 12 Oct 2014 22:41:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdVZ8-0001Pu-3P for emacs-devel@gnu.org; Sun, 12 Oct 2014 22:40:59 -0400 Original-Received: from world.peace.net ([96.39.62.75]:38670) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdVZ7-0001Pp-VU; Sun, 12 Oct 2014 22:40:54 -0400 Original-Received: from c-24-62-95-23.hsd1.ma.comcast.net ([24.62.95.23] helo=jojen) by world.peace.net with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1XdVZ1-000315-2q; Sun, 12 Oct 2014 22:40:47 -0400 In-Reply-To: <87zjd1z0yl.fsf@fencepost.gnu.org> (David Kastrup's message of "Sun, 12 Oct 2014 18:50:42 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 96.39.62.75 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:175296 Archived-At: David Kastrup writes: > libunistring (which is what GUILE currently uses for UTF-8 processing) > has a _closed_ set of recovery strategies. As it stands, it is useless > for implementing Emacs-like behavior because "encode invalid bytes into > something libunistring can deal with transparently" is not part of its > recovery strategies. Once you _have_ a useful encoding into the space > of properly working strings, _any_ recovery strategy is easy to > implement on top of that. > > For a platform, being forced to a closed set of behaviors is an > extremely limiting choice. How many times do I have to repeat it? I agree we should provide an *option* for doing what you want. No matter how many times I say it, you keep pretending that I didn't say it, and spreading FUD about Guile "forcing" policies on applications. What you wrote above simply shows your ignorance of Guile. Yes, we use libunistring for some things, but we do _not_ use it for character encoding conversions. For that we use iconv, which gives us all the tools we need to provide Emacs-like behavior. Stop setting up strawmen and hacking away at them. I've got better things to do with my time than countering your endless stream of FUD, which by now has been featured on LWN. Mark