Re: Tip: when your terminal gets all screwed up

On Sat, Nov 11, 2017 at 1:34 PM, jdow wrote: > On 2017-11-11 04:26, Tom H wrote: >> >> So it should be: >> >> PS1="\[\e[0m\][\u@\h:\l \w]\$ " > > Maybe. I got silly and experimented. > > PS1="\[\e[1m\][\u@\h:\l \w]\$ " > and > PS1="\e[1m[\u@\h:\l \w]\$ " > and >

Re: EPEL and revisions

On 11/11/2017 06:28 AM, Nico Kadel-Garcia wrote: In my experience, Nux! will respond to a request in a couple of days. If RHEL does respond, it will be in a couple of years. Nux! is the best bet. Who is "Nux!" ? https://li.nux.ro/

Re: Tip: when your terminal gets all screwed up

On 2017-11-11 04:26, Tom H wrote: So it should be: PS1="\[\e[0m\][\u@\h:\l \w]\$ " Maybe. I got silly and experimented. PS1="\[\e[1m\][\u@\h:\l \w]\$ " and PS1="\e[1m[\u@\h:\l \w]\$ " and PS1="\e[1m[\\u@\\h:\\l \\w]\$ " all produce the same thing, which leaves the issue even more confused

Re: Tip: when your terminal gets all screwed up

On 2017-11-11 06:30, Nico Kadel-Garcia wrote: On Sat, Nov 11, 2017 at 8:10 AM, Tom H wrote: [ Hundreds of lines of fine-tuning prompt manipulation code and theory snipped, especially involving quote handling ] And *this* is why I ignore it all and just use "stty sane"

Re: Tip: when your terminal gets all screwed up

On 2017-11-11 03:28, Tom H wrote: On Fri, Nov 10, 2017 at 10:15 PM, Steven Haigh wrote: For what its worth, I've been using this for years: PS1="\[\033[01;37m\]\$? \$(if [[ \$? == 0 ]]; then echo \"\[\033[01;32m\] \342\234\223\"; else echo \"\[\033[01;31m\]\342\234\227\";

Re: [EXTERNAL] Re: Tip: when your terminal gets all screwed up

Or just “reset”. -Miles On Nov 11, 2017, at 08:33, Steven Haigh > wrote: On Sunday, 12 November 2017 1:30:45 AM AEDT Nico Kadel-Garcia wrote: On Sat, Nov 11, 2017 at 8:10 AM, Tom H > wrote: [ Hundreds of

Re: Tip: when your terminal gets all screwed up

On Sat, Nov 11, 2017 at 9:30 AM, Nico Kadel-Garcia wrote: > On Sat, Nov 11, 2017 at 8:10 AM, Tom H wrote: > [ Hundreds of lines of fine-tuning prompt manipulation code and theory > snipped, especially involving quote handling ] Hundreds?! Hopefully

Re: Tip: when your terminal gets all screwed up

On 11 November 2017 at 14:33, Steven Haigh wrote: > On Sunday, 12 November 2017 1:30:45 AM AEDT Nico Kadel-Garcia wrote: >> On Sat, Nov 11, 2017 at 8:10 AM, Tom H wrote: >> >> [ Hundreds of lines of fine-tuning prompt manipulation code and theory >> snipped,

Re: Tip: when your terminal gets all screwed up

On Sunday, 12 November 2017 1:30:45 AM AEDT Nico Kadel-Garcia wrote: > On Sat, Nov 11, 2017 at 8:10 AM, Tom H wrote: > > [ Hundreds of lines of fine-tuning prompt manipulation code and theory > snipped, especially involving quote handling ] > > And *this* is why I ignore

Re: Tip: when your terminal gets all screwed up

On Sat, Nov 11, 2017 at 8:10 AM, Tom H wrote: [ Hundreds of lines of fine-tuning prompt manipulation code and theory snipped, especially involving quote handling ] And *this* is why I ignore it all and just use "stty sane" when my console gets confused.

Re: EPEL and revisions

On Fri, Nov 10, 2017 at 5:26 PM, ToddAndMargo wrote: > Dear List, > > I learned something I did not realize about EPEL > (Extra Packages for Enterprise Linux): > > > https://fedoraproject.org/wiki/EPEL#What_is_Extra_Packages_for_Enterprise_Linux_.28or_EPEL.29.3F > >

Re: Tip: when your terminal gets all screwed up

On Fri, Nov 10, 2017 at 10:15 PM, Steven Haigh wrote: > > For what its worth, I've been using this for years: > PS1="\[\033[01;37m\]\$? \$(if [[ \$? == 0 ]]; then echo \"\[\033[01;32m\] > \342\234\223\"; else echo \"\[\033[01;31m\]\342\234\227\"; fi) $(if [[ ${EUID} > == 0 ]];

Re: Tip: when your terminal gets all screwed up

On Fri, Nov 10, 2017 at 7:21 PM, jdow wrote: > On 2017-11-10 15:14, ToddAndMargo wrote: >> >> 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