From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Display corruption with binary files
Date: Sat, 25 Nov 2006 13:04:50 +0200 [thread overview]
Message-ID: <ulklz6b3h.fsf@gnu.org> (raw)
In-Reply-To: <YWU9h.24263$E02.9814@newsb.telia.net> (message from August Karlstrom on Sat, 25 Nov 2006 10:30:16 GMT)
> From: August Karlstrom <fusionfive@comhem.se>
> Date: Sat, 25 Nov 2006 10:30:16 GMT
> >
> > Bits of the binary file being interpreted at terminal control
> > characters is a likely culprit.
>
> OK, but isn't a binary file as well as a text file really just a
> sequence of arbitrary bytes?
>
> > If that is the problem then Emacs should not send such characters to
> > the terminal. It may be a terminal problem though. I'd report it as
> > an Emacs bug with that caveat.
>
> Eli Zaretskii's answer seems to indicate that this is a known problem.
Yes, it's a known problem that the Unix terminal interprets certain
sequences of characters as commands. I'm not sure Emacs can do
anything to solve this, but suggestions are welcome.
next prev parent reply other threads:[~2006-11-25 11:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 22:05 Display corruption with binary files August Karlstrom
2006-11-24 11:49 ` Robert Thorpe
2006-11-25 10:30 ` August Karlstrom
2006-11-25 11:04 ` Eli Zaretskii [this message]
2006-11-25 16:38 ` Perry Smith
2006-11-25 21:02 ` Eli Zaretskii
2006-11-26 0:34 ` Perry Smith
2006-11-26 4:09 ` Eli Zaretskii
2006-11-26 4:55 ` Perry Smith
2006-11-26 9:19 ` Arjen Wiersma
2006-11-26 20:23 ` Eli Zaretskii
[not found] ` <mailman.1101.1164472694.2155.help-gnu-emacs@gnu.org>
2006-11-26 13:30 ` Robert Thorpe
2006-11-25 12:42 ` Peter Dyballa
[not found] ` <mailman.1089.1164458537.2155.help-gnu-emacs@gnu.org>
2006-11-25 13:16 ` August Karlstrom
[not found] ` <mailman.1086.1164452697.2155.help-gnu-emacs@gnu.org>
2006-11-27 20:50 ` Stefan Monnier
2006-11-24 18:37 ` Eli Zaretskii
[not found] ` <mailman.1054.1164416983.2155.help-gnu-emacs@gnu.org>
2006-11-25 10:30 ` August Karlstrom
2006-11-25 10:42 ` August Karlstrom
2006-11-25 13:15 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ulklz6b3h.fsf@gnu.org \
--to=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).