[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash 4.4.18 return to new line
From: |
Alexander Kozlenkov |
Subject: |
Re: bash 4.4.18 return to new line |
Date: |
Sun, 04 Feb 2018 15:09:28 +0000 |
I bracketed \[ and \] each prompt variables and simple symbols and line
break does work right.
Example:
> \[\e[1;32m\]\u\[\e[m\]\[\e[1;32m\]@\[\e[m\]\[\e[1;32m\]\h\[\e[m\]
But if I bracketed sequences some symbols, line break does not work .
Example:
> \[\e[1;32m\]\u@\h\[\e[m\]
And thanks for You help!
--
Best regards
Alexandr Kozlenkov
вс, 4 февр. 2018 г. в 2:04, Chet Ramey <chet.ramey@case.edu>:
> On 2/3/18 2:21 AM, Alexander Kozlenkov wrote:
> > I changed my PS1 to:
> > (cmd):09:37:53:sah4ez@PC001:~$ printenv PS1
> > \e[1;95m\t\]\e[0m:\]\e[0;92m\u@\h\]\e[0m:\]\e[0;34m\w\a\]\]\e[0m$ \]
>
> The output of printenv indicates that you have non-printing characters in
> PS1 that are not bracketed by \[ and \]. In fact, there don't seem to be
> any \[ sequences in the prompt string at all (and you have two \] in a
> row?).
>
> The mode strings appear to be properly bracketed using \1 and \2.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
> ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
>
- bash 4.4.18 return to new line, Alexander Kozlenkov, 2018/02/02
- Re: bash 4.4.18 return to new line, Chet Ramey, 2018/02/02
- Re: bash 4.4.18 return to new line, Alexander Kozlenkov, 2018/02/02
- Re: bash 4.4.18 return to new line, Chet Ramey, 2018/02/02
- Re: bash 4.4.18 return to new line, Alexander Kozlenkov, 2018/02/03
- Re: bash 4.4.18 return to new line, Chet Ramey, 2018/02/03
- Re: bash 4.4.18 return to new line,
Alexander Kozlenkov <=
- Re: bash 4.4.18 return to new line, Chet Ramey, 2018/02/04
- Re: bash 4.4.18 return to new line, Alexander Kozlenkov, 2018/02/04
- Re: bash 4.4.18 return to new line, Chet Ramey, 2018/02/04