Color escape sequences are not correctly shown in terminal about bashly

[DannyBen]

This is weird. Not sure how to reproduce it, as we are both on Ubuntu.

Maybe you can send me the output of your env command minus any secrets or positively unrelated vars?

[DannyBen]

@EmilySeville7cfg I am guessing that if you run the below command you get the same unescaped codes?

$ ruby -r readline -e 'Readline.readline "\n\e[33m\e[1mbashly\e[0m > "'

Bashly terminal is using Ruby's built in Readline behind the scenes, which simply has a prompt as a first argument, which should support escaping.

What does your ruby -v say?

[EmilyGraceSeville7cf]

Maybe you can send me the output of your env command minus any secrets or positively unrelated vars?

COLORTERM=truecolor
SHELL=/usr/bin/nu
TERM=xterm-256color

@EmilySeville7cfg I am guessing that if you run the below command you get the same unescaped codes?

That's true:

What does your ruby -v say?

ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]

[DannyBen]

Thanks - I will take a deeper look.

Does this following command make any difference? (added semicolons to the escape):

$ ruby -r readline -e 'Readline.readline "\n\e[33;1mbashly\e[0m > "'

[EmilyGraceSeville7cf]

Does this following command make any difference? (added semicolons to the escape):

@DannyBen, not at all:

[DannyBen]

Not sure how to reproduce. I thought i might be nushell, or your Ruby - but I tested both and see the colors.

[DannyBen]

I went with the "if you can't fix it, eliminate it" approach. The prompt is now colorless, and looks like the bashly logo:
$> bashly

[DannyBen]

Released in 1.0.6.