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: Tue, 07 Oct 2014 18:03:22 +0200 Message-ID: <87vbnvamut.fsf@fencepost.gnu.org> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412697851 32021 80.91.229.3 (7 Oct 2014 16:04:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Oct 2014 16:04:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 07 18:04:04 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 1XbXF4-0005Eu-VY for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 18:04:03 +0200 Original-Received: from localhost ([::1]:59719 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXF4-00024Y-KA for ged-emacs-devel@m.gmane.org; Tue, 07 Oct 2014 12:04:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35278) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXEe-0001UL-EY for emacs-devel@gnu.org; Tue, 07 Oct 2014 12:03:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbXEb-0006yj-VO for emacs-devel@gnu.org; Tue, 07 Oct 2014 12:03:36 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43316) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXEb-0006yf-T0 for emacs-devel@gnu.org; Tue, 07 Oct 2014 12:03:33 -0400 Original-Received: from localhost ([127.0.0.1]:50490 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbXEb-0005P9-EE; Tue, 07 Oct 2014 12:03:33 -0400 Original-Received: by lola (Postfix, from userid 1000) id 3D17CE060A; Tue, 7 Oct 2014 18:03:22 +0200 (CEST) In-Reply-To: (Andreas Schwab's message of "Tue, 07 Oct 2014 17:42:39 +0200") 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:175080 Archived-At: 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. -- David Kastrup