From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andreas Schwab Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Tue, 07 Oct 2014 19:38:30 +0200 Message-ID: <87vbnvwzjd.fsf@igel.home> References: <54193A70.9020901@member.fsf.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> <87ppe5rt5l.fsf@uwakimon.sk.tsukuba.ac.jp> <87d2a4arju.fsf@fencepost.gnu.org> <878ukrc2sr.fsf@fencepost.gnu.org> <87vbnvamut.fsf@fencepost.gnu.org> <87mw97alvn.fsf@fencepost.gnu.org> <87iojvakl9.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412703556 17277 80.91.229.3 (7 Oct 2014 17:39:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Oct 2014 17:39:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 07 19:39: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 1XbYj5-0001Q6-Qh for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 19:39:07 +0200 Original-Received: from localhost ([::1]:60080 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbYj5-0000iD-9a for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 13:39:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbYil-0000hv-6t for emacs-devel@gnu.org; Tue, 07 Oct 2014 13:38:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbYig-0000z8-Aa for emacs-devel@gnu.org; Tue, 07 Oct 2014 13:38:47 -0400 Original-Received: from cantor2.suse.de ([195.135.220.15]:37124 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbYia-0000xp-Ud; Tue, 07 Oct 2014 13:38:37 -0400 Original-Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id EC42EAB08; Tue, 7 Oct 2014 17:38:35 +0000 (UTC) X-Yow: While I'm in LEVITTOWN I thought I'd like to see the NUCLEAR FAMILY!! In-Reply-To: <87iojvakl9.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 07 Oct 2014 18:52:18 +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.2.x-3.x (no timestamps) [generic] X-Received-From: 195.135.220.15 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:175089 Archived-At: David Kastrup writes: > Andreas Schwab writes: > >> David Kastrup writes: >> >>> Andreas Schwab writes: >>> >>>> David Kastrup writes: >>>> >>>>> Andreas Schwab writes: >>>>> >>>>>> David Kastrup writes: >>>>>> >>>>>>> Andreas Schwab writes: >>>>>>> >>>>>>>> David Kastrup writes: >>>>>>>> >>>>>>>>> One problem with that is that quite often Emacs' choice of a coding >>>>>>>>> system for a buffer is the result of heuristics rather than dependable >>>>>>>>> information. Not making a fuzz might often be simplest. >>>>>>>> >>>>>>>> If you try to save a buffer Emacs will check whether all characters are >>>>>>>> encodable, and complain (and ask) if they aren't. >>>>>>> >>>>>>> Sure, but a raw byte is trivially encodable since it is no character. >>>>>> >>>>>> This is a contradiction. It isn't a character, so it isn't encodable. >>>>> >>>>> The character representation of "raw byte" is trivially encodable since >>>>> it represents a single byte in any encoding. >>>> >>>> No encoding (except raw-text) can encode characters from the eight-bit >>>> charset. >>> >>> (encode-coding-string (string (decode-char 'eight-bit 128)) 'utf-8) >>> => "\200" >> >> That's what you get if you *force* the coding system. > > It would appear that you are forcing your logic. "No encoding can ..." > does not mean that. That's what Emacs told me, with the heuristics you are talking about. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."