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: Inadequate documentation of silly characters on screen. Date: Sun, 22 Nov 2009 00:30:46 +0100 Organization: Organization?!? Message-ID: <87my2f8nh5.fsf@lola.goethe.zz> References: <20091118191258.GA2676@muc.de> <20091119082040.GA1720@muc.de> <87aayitvoy.fsf@wanchan.jasonrumney.net> <87ocmyf6so.fsf@catnip.gol.com> <87vdh57tp2.fsf@uwakimon.sk.tsukuba.ac.jp> <878we1ekb0.fsf@uwakimon.sk.tsukuba.ac.jp> <87hbso347j.fsf@uwakimon.sk.tsukuba.ac.jp> <877htk2xbk.fsf@uwakimon.sk.tsukuba.ac.jp> <87lji0awh8.fsf@lola.goethe.zz> <876394dlsr.fsf@uwakimon.sk.tsukuba.ac.jp> <877htkaqri.fsf@lola.goethe.zz> <87y6lzdat8.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1258846295 11393 80.91.229.12 (21 Nov 2009 23:31:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Nov 2009 23:31:35 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 22 00:31:28 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NBzQM-0004rX-OB for ged-emacs-devel@m.gmane.org; Sun, 22 Nov 2009 00:31:27 +0100 Original-Received: from localhost ([127.0.0.1]:46039 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBzQM-000288-7C for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 18:31:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBzQF-00025T-LX for emacs-devel@gnu.org; Sat, 21 Nov 2009 18:31:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBzQA-00020c-CA for emacs-devel@gnu.org; Sat, 21 Nov 2009 18:31:18 -0500 Original-Received: from [199.232.76.173] (port=43346 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBzQA-00020Z-88 for emacs-devel@gnu.org; Sat, 21 Nov 2009 18:31:14 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:51216) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NBzQ9-0004wp-PH for emacs-devel@gnu.org; Sat, 21 Nov 2009 18:31:14 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NBzQ5-0004nV-8G for emacs-devel@gnu.org; Sun, 22 Nov 2009 00:31:09 +0100 Original-Received: from p5b2c26da.dip.t-dialin.net ([91.44.38.218]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Nov 2009 00:31:09 +0100 Original-Received: from dak by p5b2c26da.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Nov 2009 00:31:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 27 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c26da.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:GDSavAUFopa8LeihV5qX7fJR12Y= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:117475 Archived-At: "Stephen J. Turnbull" writes: > David Kastrup writes: > > "Stephen J. Turnbull" writes: > > > > I meant pre-existing corruption [...] > > > > That interpretation is not the business of the editor. > > Precisely my point. The editor has *no* way to interpret at the point > of encountering the invalid sequence, and therefore it should *stop* > and ask the user what to do. That doesn't mean it should throw away > the data, but it sure does mean that it should not continue as though > there is valid data in the buffer. > > Emacs is welcome to do that, but I am sure you will get bug reports > about it. Why would we get a bug report about Emacs saving a file changed only in the locations that the user actually edited? People might complain when Emacs does not recognize some encoding properly, but they certainly will not demand that Emacs should stop working altogether. -- David Kastrup