SCIENTIFIC-LINUX-USERS Archives

November 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Fri, 10 Nov 2017 18:48:23 -0800
Reply-To:
Message-ID:
Content-Transfer-Encoding:
quoted-printable
Subject:
From:
Content-Type:
text/plain; charset=utf-8; format=flowed
In-Reply-To:
MIME-Version:
1.0
Comments:
Parts/Attachments:
text/plain (37 lines)
On 2017-11-10 16:38, ToddAndMargo wrote:
> On 11/10/2017 04:21 PM, jdow wrote:
>> 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
> 
> Sweet!
Here is what I have in my .bash_profile file:


if [ "$PS1" ]; then
   # extra [ in front of \u unconfuses confused Linux VT parser
   PS1="\e[0 [[\\u@\\h:\\l \\w]\\$ "
fi

{^_^}

ATOM RSS1 RSS2