public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: David Csercsics <david@really.isa-geek.net>
To: "Speakup is a screen review system for Linux."
	<speakup@braille.uwo.ca>, Cheryl Homiak <chomiak@charter.net>
Subject: Re: tty in weird character mode
Date: Tue, 13 Apr 2004 20:14:37 -0700	[thread overview]
Message-ID: <0HW500A3R4TV9I@l-daemon> (raw)
In-Reply-To: <Pine.LNX.4.58.0404132138220.3318@maranatha.charter.net>

>The tty problem reminded me that I wanted to ask this. I don't know how to
>explain this technically, but it usually happens when you've accidentally
>put a file through "more' that wasn't really text but didn't give you a
>complaint from more, or if you accidentally use less when you should have
>used zless. Can't think of other incidents where it happens though there
>probably are others. Anyway, even though you can quit the program, what
>appears on your console from then on, whether typing or reading, is not
>intelligible; i don't know if it's converting to binary or another
>character set--I would think maybe binary. Neither logging out (you can
>do it but your loggin prompt and command prompt after you've logged in
>come out in the same characters) or killing
>the tty does any good and while I can use the rest of my system fine, if I
>really want that tty back I eventually have to succumb and reboot. Is there
>a way around this? I hope I've explained it well enough for somebody to
>know what I'm talking about. I suppose I could make it happen and paste
>some of the result here but I'd rather not do it.
>Thanks.

Well have you tried just typing reset at your prompt. That will cause
the shell to reset your terminal so that it works correctly.


  parent reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Gregory Nowak
 ` Doug Sutherland
   ` Cheryl Homiak
 ` David Csercsics [this message]
 ` Kenny Hitt
   ` Sound card recommendations? Al Puzzuoli
 ` tty in weird character mode Garrett Klein

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0HW500A3R4TV9I@l-daemon \
    --to=david@really.isa-geek.net \
    --cc=chomiak@charter.net \
    --cc=speakup@braille.uwo.ca \
    /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).