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 18:16:21 +0200 Message-ID: References: <54193A70.9020901@member.fsf.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> <87ppe5rt5l.fsf@uwakimon.sk.tsukuba.ac.jp> <87d2a4arju.fsf@fencepost.gnu.org> <878ukrc2sr.fsf@fencepost.gnu.org> <87vbnvamut.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412698611 10653 80.91.229.3 (7 Oct 2014 16:16:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Oct 2014 16:16:51 +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 18:16:44 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 1XbXRL-0005jM-3Q for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 18:16:43 +0200 Original-Received: from localhost ([::1]:59801 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXRK-0008JN-J4 for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 12:16:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38858) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXRB-0008Bf-Rm for emacs-devel@gnu.org; Tue, 07 Oct 2014 12:16:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbXR6-0002sp-KG for emacs-devel@gnu.org; Tue, 07 Oct 2014 12:16:33 -0400 Original-Received: from cantor2.suse.de ([195.135.220.15]:34817 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXR0-0002rL-SN; Tue, 07 Oct 2014 12:16:23 -0400 Original-Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 2C10EAB07; Tue, 7 Oct 2014 16:16:22 +0000 (UTC) X-Yow: By MEER biz doo SCHOIN.. In-Reply-To: <87vbnvamut.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 07 Oct 2014 18:03:22 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (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:175082 Archived-At: 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. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."