Code looks good to me! I'm not sure if we should also implement the delay that was proposed in #4799:

When a new window is created, use a blank title and delay the ghost emoji in the titlebar for something like 500ms, and only set it if another title hasn't been set. That should give the shell enough time to startup and set a title if there is one.

... but this change looks like a step in the right direction improvement-wise.

Thank you for the review!

I noticed that the flickering issue is more complex than initially thought. The current flickering isn't just about the ghost emoji - it's also related to how the title (folder emoji + path) gets updated.

Even with the 500ms delay for the ghost emoji, I still see a brief flash where the folder emoji appears before the path. This suggests that the issue might be more related to the title update mechanism itself rather than just the ghost emoji timing.

I believe this current implementation is a good first step as it addresses the original issue about the ghost emoji's white flash. For the broader title update flickering, we might want to:

1. First validate if this improvement helps with the original issue
2. Create a separate issue to track and investigate the title update mechanism if needed

What do you think?

I believe this current implementation is a good first step as it addresses the original issue about the ghost emoji's white flash. For the broader title update flickering, we might want to:

1. First validate if this improvement helps with the original issue
2. Create a separate issue to track and investigate the title update mechanism if needed

What do you think?

I think that sounds right. Maybe do (1) as part of this PR's scope before merging it?

I think that sounds right. Maybe do (1) as part of this PR's scope before merging it?

Yes, but if there are better suggestions or directions, I don’t mind improving this PR further.

The direction looks good. I think we should continue improving this PR though. For one, I don't like that if nothing ever sets a title then the window is just blank. To be fair, MOST shells (esp with our shell integration) should set the title, but if you run a command or something it will not. That's why I suggested the timer to fallback to a default eventually.

but if you run a command or something it will not.

Interesting case, I hadn't considered a similar scenario before.

I've made a commit to improve this scenario by:

• Adding a 500ms fallback timer for "👻"
• Canceling timer if title is set

While I haven't been able to observe this edge case in my testing environment, the improvement should provide a more robust solution for such scenarios.