home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!wupost!gumby!destroyer!ubc-cs!edmonds
- From: edmonds@cs.ubc.ca (Brian Edmonds)
- Newsgroups: comp.os.linux
- Subject: Re: catting binaries
- Message-ID: <1992Jul31.054106.23515@cs.ubc.ca>
- Date: 31 Jul 92 05:41:06 GMT
- References: <1992Jul31.044152.18121@athena.mit.edu>
- Sender: usenet@cs.ubc.ca (Usenet News)
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Lines: 20
-
- f6930910@scheme.cs.ubc.ca (from UBC :) wrote:
- >The wierd thing is that sometimes (not allways), after all the
- >garbage has been cat(ed) to the screen, the terminal is left in
- >a state such that all characters echoed to the screen are displayed
- >as IBM extended graphics characters. This does not allways happen, but
- >usually does. To see this, just cat a few of your favorite binaries
- >to stdout.
- It's quite simple really. The vt terminal emulation has been expanded
- to handle the IBM extended character set. When the driver receives
- a ^N, it kicks into extended mode, and interprets characters in their
- new, wild, and wonderful form. :) To get back to normal mode, simply
- output a ^O to the screen. (This can by done with echo: echo ^V^O)
-
- You should be able to duplicate this effect using any terminal program
- with _full_ VT100 emulation. I'm making this a general posting, as it
- is a problem which perplexed me for a long time a number of years back
- (not with Linux obviously).
-
- ----------------------------------------------------------------------
- Brian Edmonds (MSc CompSci) edmonds@cs.ubc.ca
-