Re: PS0 issue with escape sequence

2016-09-17 Thread Benoît Dejean
On Sat, Sep 17, 2016 at 04:57:08PM -0400, Chet Ramey wrote: > On 9/17/16 4:47 PM, Benoît Dejean wrote: > > On Sat, Sep 17, 2016 at 01:12:24PM -0400, Chet Ramey wrote: > >> On 9/16/16 9:25 PM, Ben wrote: > >>> Hello, > >>> > >>> using bash-4.4, setting PS0 to '\[\033[1;36m\]started at > >>>

Re: PS0 issue with escape sequence

2016-09-17 Thread Chet Ramey
On 9/17/16 4:47 PM, Benoît Dejean wrote: > On Sat, Sep 17, 2016 at 01:12:24PM -0400, Chet Ramey wrote: >> On 9/16/16 9:25 PM, Ben wrote: >>> Hello, >>> >>> using bash-4.4, setting PS0 to '\[\033[1;36m\]started at >>> \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02 >>> prefix and

Re: PS0 issue with escape sequence

2016-09-17 Thread Chet Ramey
On 9/16/16 9:25 PM, Ben wrote: > Hello, > > using bash-4.4, setting PS0 to '\[\033[1;36m\]started at > \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02 > prefix and suffix. Yes, those are the expansions of the \[ and \] escape sequences. Since $PS0 is not being passed to

PS0 issue with escape sequence

2016-09-16 Thread Ben
Hello, using bash-4.4, setting PS0 to '\[\033[1;36m\]started at \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02 prefix and suffix. 01 02 73 74 61 72 74 65 64 20 61 74 20 30 33 3a |..started at 03:| 0010 31 38 3a 30 37 01 02 0a