ANSI characters appearing after setting the title

[trajano]

Windows Terminal version (or Windows build number)

Microsoft Windows [Version 10.0.19042.985]

Other Software

'git' (2.31.1.windows.1) from scoop and using that as the Bash provider
'aws' (2.2.5) AWS CLI that this is having problems with

Steps to reproduce

When I do

aws logs tail --follow --region us-west-2 --since 0s my-cloudwatch-logs

I see the colors correctly, but when I set the title as follows

echo -ne "\033]0;☁ my-cloudwatch-logs \a" && aws logs tail --follow --region us-west-2 --since 0s my-cloudwatch-logs

The colors stop working and I see the ANSI escape codes.

This used to work before I reinstalled Windows

Expected Behavior

Colors should appear and not ANSI codes. Title should get set.

Actual Behavior

ANSI Codes are appearing. Title is getting set.

[skyline75489]

By saying "colors" do you mean the colored output in the console? A screenshot would be nice.

[zadjii-msft]

Also, does

echo -ne "\033]0;my-cloudwatch-logs \a" && aws logs tail --follow --region us-west-2 --since 0s my-cloudwatch-logs

work as expected?

[trajano]

direct has color

No color when setting the title

[zadjii-msft]

Definitely another case of VT processing being disabled, though I don't know why this wouldn't work when preceeded by an echo. We've got a pile of these elsewhere on the repo, but this one seems different. I don't have any idea why the echo in the same commandline would disable this.

I wonder if

printf "\033]0;☁ my-cloudwatch-logs \a" && aws logs tail --follow --region us-west-2 --since 0s my-cloudwatch-logs

would work instead?

[trajano]

@zadjii-msft yup I was actually hesitant on creating another one, but this is a very weird and specific scenario. As for your scenario nope it did not work.

Here's something to narrow it down. I used true rather than echo and it worked as expected. So it may be something to do with the title or the ANSI sequence.

Actually echo X && .... and printf X also didn't work so it may be something to do with writing an output

sleep 1 && ... works correctly.

curl -L https://get.scoop.sh && ... also works correctly. so that disproves my hypothesis where it's because I had an output.

My hypothesis right now is anything that uses msys that generates an output will prevent this from working correctly.

So far the hypothesis is showing it because date && ... also does not work.

[zadjii-msft]

so this sounds like something that must have recently regressed in msys, between whatever version you had before you reinstalled windows and whatever's currently installed. Maybe this should get moved upstream?

[trajano]

It's actually the same version. But I had a fresh install of Windows so I am not sure.

[trajano]

Hypothesis confirmed I use powershell to execute. So it may be something in msys that git is using.

Except I can't seem to write out the escape sequence in powershell correctly.

[zadjii-msft]

oh woah, this actually looks exactly like #9607, with a touch of #6634

[trajano]

@zadjii-msft the difference betweem #9607 and this is that aws actually processes the data now. But my comment in #6634 which points to starship/starship#2258 (comment) actually gave me the workaround I need

Basically I have to close off the stdin

(echo -ne "\033]0;☁ title  \a" < /dev/null)

Closing this for now since I have a workaround and it appears to be an upstream msys/cygwin issue @zadjii-msft feel free to re-open if you need to.