From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Display corruption with binary files Date: Sun, 26 Nov 2006 22:23:19 +0200 Message-ID: References: <1164368979.309609.307320@45g2000cws.googlegroups.com> <4EEF30F4-FEE1-499D-8302-22959717A64D@easesoftware.com> <16D0F7A9-0BEF-4513-BD37-A76CA67F0952@easesoftware.com> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1164572619 30288 80.91.229.2 (26 Nov 2006 20:23:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 26 Nov 2006 20:23:39 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Nov 26 21:23:35 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GoQXE-0000qz-IW for geh-help-gnu-emacs@m.gmane.org; Sun, 26 Nov 2006 21:23:33 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GoQXD-0008I1-Vc for geh-help-gnu-emacs@m.gmane.org; Sun, 26 Nov 2006 15:23:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GoQX2-0008H2-2T for help-gnu-emacs@gnu.org; Sun, 26 Nov 2006 15:23:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GoQX0-0008FH-E9 for help-gnu-emacs@gnu.org; Sun, 26 Nov 2006 15:23:19 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GoQX0-0008FE-AS for help-gnu-emacs@gnu.org; Sun, 26 Nov 2006 15:23:18 -0500 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GoQX0-0008UK-3z for help-gnu-emacs@gnu.org; Sun, 26 Nov 2006 15:23:18 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-245-215.inter.net.il [84.228.245.215]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id GJN28370 (AUTH halo1); Sun, 26 Nov 2006 22:23:16 +0200 (IST) Original-To: help-gnu-emacs@gnu.org In-reply-to: <16D0F7A9-0BEF-4513-BD37-A76CA67F0952@easesoftware.com> (message from Perry Smith on Sat, 25 Nov 2006 22:55:45 -0600) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:39024 Archived-At: > Cc: help-gnu-emacs@gnu.org > From: Perry Smith > Date: Sat, 25 Nov 2006 22:55:45 -0600 > > On Nov 25, 2006, at 10:09 PM, Eli Zaretskii wrote: > > >> Cc: help-gnu-emacs@gnu.org > >> From: Perry Smith > >> Date: Sat, 25 Nov 2006 18:34:04 -0600 > >> > >> On my Mac system, there is a version of emacs 21.2.1 in /usr/bin/ > >> emacs. I have a bzip tar file. I type: > >> > >> emacs foo.tar.bz2 > >> > >> from a Mac "terminal" window (not an X11 window) and it comes up just > >> fine: inside the terminal. I can move around just like I remember. > > > > Maybe whoever built that version of Emacs for the Mac did something > > special to it. > > I get the same results with the emacs on the RS/6000 that I built > personally. I simple did configure and make. That emacs is 21.4.1. Okay, I see that I've misunderstood the point and responded in a way that could cause a terrible confusion. Let me try to clarify. Yes, Emacs does display control characters as ^c or \XXX. However, it does so only for certain characters (mainly, 8-bit characters and low-end 7-bit characters). It is quite possible that an arbitrary binary garbage could be interpreted by Emacs as non-ASCII characters and cause some terminal control sequence be written to the display. Also, I think control characters that come from a display table (for those who know what that is) are output verbatim. So, to summarize, Emacs mostly does TRT with unprintable characters, but not always, and visiting a binary file in the default multibyte mode could plausibly cause related problems. Sorry for any confusion I could have caused with my earlier messages in this thread.