From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Mon, 06 Oct 2014 18:40:30 +0200 Message-ID: <877g0ddudd.fsf@fencepost.gnu.org> References: <54193A70.9020901@member.fsf.org> <83iokato6x.fsf@gnu.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> <87fvf1dxha.fsf@fencepost.gnu.org> <83d2a5maib.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412616762 2465 80.91.229.3 (6 Oct 2014 17:32:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Oct 2014 17:32:42 +0000 (UTC) Cc: rms@gnu.org, mhw@netris.org, dmantipov@yandex.ru, emacs-devel@gnu.org, handa@gnu.org, monnier@iro.umontreal.ca, stephen@xemacs.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 06 19:32:35 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 1XbC9B-0002hS-Dm for ged-emacs-devel@m.gmane.org; Mon, 06 Oct 2014 19:32:33 +0200 Original-Received: from localhost ([::1]:53352 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbC9A-0000rY-Us for ged-emacs-devel@m.gmane.org; Mon, 06 Oct 2014 13:32:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35272) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbC8x-0000rT-8M for emacs-devel@gnu.org; Mon, 06 Oct 2014 13:32:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbC8w-0007QV-8l for emacs-devel@gnu.org; Mon, 06 Oct 2014 13:32:19 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47611) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbC8w-0007QP-6C for emacs-devel@gnu.org; Mon, 06 Oct 2014 13:32:18 -0400 Original-Received: from localhost ([127.0.0.1]:54783 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbC8m-0003yw-8u; Mon, 06 Oct 2014 13:32:08 -0400 Original-Received: by lola (Postfix, from userid 1000) id 5DE18E0489; Mon, 6 Oct 2014 18:40:30 +0200 (CEST) In-Reply-To: <83d2a5maib.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Oct 2014 19:24:44 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:175028 Archived-At: Eli Zaretskii writes: >> From: David Kastrup >> Cc: Mark H Weaver , rms@gnu.org, >> monnier@iro.umontreal.ca, dmantipov@yandex.ru, emacs-devel@gnu.org, >> handa@gnu.org, stephen@xemacs.org >> Date: Mon, 06 Oct 2014 17:33:21 +0200 >> >> If an overlong UTF-8 byte sequence representing '"' is processed >> transparently by Emacs, it will be reencoded into the original >> afterwards and depending on the next processing stage might trip up >> software afterwards. > > Indeed. But that's what is expected from an editor: not to change the > stuff the user didn't touch. > >> Of course, it would have done equally so without Emacs (or GUILE) in >> the middle. > > Right. > >> The solution obviously is to use a coding scheme for recoding that >> does _not_ reproduce unencodable bytes. > > An editor such as Emacs cannot do that, I think. It sure can. Saving with a different encoding system than the one one started with is always an option. Not all encoding system variants need to be lossless, and the choice how to treat non-encodable bytes can be part of the coding system variant. -- David Kastrup