Reset garbled Terminal window on OS X

6,973

Solution 1

Your terminal has been shifted into “alternate character set” mode. To shift it back out, type

tput rmacs

at your (garbled) shell prompt. Your typing will appear garbled, too, but it will be back to normal after this command finishes.

Solution 2

I have had this same problem. To fix, click on Shell --> Send Reset. And if that doesn't work. Shell --> Hard Reset. This will reset it without you having to close and reopen the terminal.

Solution 3

Typing "reset" at the command line (even if you cannot see what you are tying) often helps.

Share:
6,973

Related videos on Youtube

conorgriffin
Author by

conorgriffin

I am an experienced engineer working for Workday in Dublin, Ireland. I have a background in development and systems engineering and love working with technology.

Updated on September 17, 2022

Comments

  • conorgriffin
    conorgriffin over 1 year

    I was connected to a linux server over SSH. After performing the following command

    cat dmesg.1.gz
    

    the prompt on my SSH session changed from conor@linux:~$ to ␌⎺┼⎺⎼@┌␋┼┤│:·/┌⎺±⎽$

    Any text I typed into the terminal was also garbled, even after disconnecting from the SSH session by typing exit, the terminal session which was now with my mac, was still garbled. I resolved the issue by closing the terminal window and opening a new one.

    Is there any way to reset the terminal without closing the window and reopening such as a key combination?

  • conorgriffin
    conorgriffin over 13 years
    Picked this as the best answer because it explained the reason why it happened in addition to resolving the issue. Mr. Mans answer worked too.
  • Kelvin
    Kelvin about 12 years
    +1 this is the only solution that worked for me, when something went wrong on the remote side of an ssh connection.
  • Will
    Will over 9 years
    ⌘R — Send Reset
  • logoff
    logoff about 9 years
    worked on a Linux terminal too :)
  • demongolem
    demongolem about 4 years
    The hard reset worked for me, but I had to wait a couple of minutes before I got the command line back. So patience may be necessary...