And that has an oops in it. Don't include the ";". The proper escape sequence would be "esc[0". My bad. Been too long since I did more than copy stuff. {^_^} On 2017-11-10 16:28, Carl Friedberg wrote: > That is cool. > > I've had (in the VT220/320) some pretty wild prompts. > > There was a thunderbolt, and for the holidays, someone > crafted Santa, a sleigh, and reindeer. People must have > had more time back then, or else no one who was in > charge had any idea what they were doing. Or both. > > Carl Friedberg > (212) 798-0718 > www.esb.com > The Elias Book of Baseball Records > 2017 Edition > > -----Original Message----- > From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of jdow > Sent: Friday, November 10, 2017 7:22 PM > To: [log in to unmask] > Subject: Re: Tip: when your terminal gets all screwed up > > On 2017-11-10 15:14, ToddAndMargo wrote: >> Dear List, >> >> Ever cat a binary file by accident and your >> terminal gets all screwed up. >> >> I had a developer on the Perl 6 chat line give me >> a tip on how to unscrew your terminal and set it >> back to normal. (He way helping me do a binary >> read from the keyboard.) >> >> stty sane^j >> >> Note: it is <ctr><J>, not "enter". >> >> -T > > Make "\033]0;" the first bit of your prompt. Never worry about it again. > > ESC-0 sets the terminal to have no attribute bits set. So it clears funny > display. I've had that as a standard part of my prompts for decades, even back > in the CP/M days. > {^_^} Joanne >