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: Displaying bytes Date: Thu, 26 Nov 2009 09:59:24 +0100 Organization: Organization?!? Message-ID: <874oohvez7.fsf@lola.goethe.zz> References: <20091119082040.GA1720@muc.de> <874ooq8xay.fsf@wanchan.jasonrumney.net> <20091119141852.GC1720@muc.de> <20091119155848.GB1314@muc.de> <87aayiihe9.fsf@lola.goethe.zz> <20091119180848.GE1314@muc.de> <47325.130.55.118.19.1258658705.squirrel@webmail.lanl.gov> <20091119212550.GG1314@muc.de> <87my2ign8u.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1259226041 31719 80.91.229.12 (26 Nov 2009 09:00:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 26 Nov 2009 09:00:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 26 10:00:34 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 1NDaD1-0008FF-6s for ged-emacs-devel@m.gmane.org; Thu, 26 Nov 2009 10:00:15 +0100 Original-Received: from localhost ([127.0.0.1]:39774 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDaD0-00016c-Rr for ged-emacs-devel@m.gmane.org; Thu, 26 Nov 2009 04:00:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDaCu-00015f-Ga for emacs-devel@gnu.org; Thu, 26 Nov 2009 04:00:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDaCp-000130-5q for emacs-devel@gnu.org; Thu, 26 Nov 2009 04:00:07 -0500 Original-Received: from [199.232.76.173] (port=45291 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDaCo-00012q-W8 for emacs-devel@gnu.org; Thu, 26 Nov 2009 04:00:03 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:35933) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NDaCo-0000oy-HO for emacs-devel@gnu.org; Thu, 26 Nov 2009 04:00:02 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NDaCa-0007xv-RQ for emacs-devel@gnu.org; Thu, 26 Nov 2009 09:59:48 +0100 Original-Received: from p5b2c2054.dip.t-dialin.net ([91.44.32.84]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Nov 2009 09:59:48 +0100 Original-Received: from dak by p5b2c2054.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Nov 2009 09:59:48 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c2054.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:LxxJB3S7kzou6gM6yj1EYHNlOKc= 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:117812 Archived-At: Richard Stallman writes: > > There pretty much shouldn't be any in multibyte buffers. > > > Would it be good to ask people to send bug reports when these > > stray byte characters appear in multibyte buffers? > > No, these chars can appear in cases where Emacs does the right thing. > I.e. sometimes they reflect bugs, but often they just reflect "pilot > errors" or corrupted data completely outside the control of Emacs. > > If it is nearly always due to a bug, a user error, or bad data, > perhaps it would be good to display a diagnostic after file commands > that put them in the buffer. Perhaps pop up a buffer explaining what > these mean and what to do about them. The encoding indicator in the mode line could get warning-face, and the respective pop-up help mention "buffer contains undecodable bytes." -- David Kastrup