Using theme with WezTerm

[Drllap]

The theme doesn't kick in the first prompt :

I'm using WezTerm. It starts bash in login mode, maybe it has something to do with that?
It works fine both in Alacritty and XTerm.
Should I create an issue?

[boldandbusted]

I'm not seeing this behavior with WezTerm, which is my "daily driver" terminal. Not sure the best approach to debugging this, however.

[Drllap]

I did a bit of experimenting and found out I had a similar issue with starship: starship/starship#5686

The issue is also present when using Aalacritty/XTerm but the difference is that WezTerm starts bash in login mode by default.

WezTerm shipps with the shell-integration file that is sourced when opening bash in login mode. Removing it fixes the issue

[boldandbusted]

So, I think this issue was resolved, but not sure how to mark it as "answered" here.

[akinomyoga]

The OP or a maintainer can mark the answer. By the way, how was this solved?

[Drllap]

This is not really solved but this isn't related to bash-it. This has something to do with the shell integration scripts shipped with WezTerm/bash-excec.
There are a couple of workarounds:

• start bash in non -login mode, then those scripts will not be sourced
• edit the script so that the bash-excec isn't executed

[akinomyoga]

Thanks. So, can the problem be reproducible just with WezTerm's shell integration and bash-preexec and without Bash-it?

Hmm, is this related (where you seem to have left comments)?

wez/wezterm#4406

In the above issue, the maintainer of WezTerm said they have worked around it, and the issue has already been closed. Does that mean the workaround was not complete?

[Drllap]

So, can the problem be reproducible just with WezTerm's shell integration and bash-preexec and without Bash-it?

Yes, this also happens with Starship: starship/starship#5686

If WezTerm is installed the shell integration scripts will be sourced no matter what terminal emulator you use as long as it opens bash in login mode (at least on my system)

In the above issue, the maintainer of WezTerm said they have worked around it, and the issue has already been closed. Does that mean the workaround was not complete?

I didn't think this was fixed but it may be. If I remember correctly, I modified the shell integration scripts locally and then stopped thinking about this. I will look into this when I have time and report back

[Drllap]

Ok, I finally got around to check this again, and this is still an issue if I use the original wezterm.sh shell integration script shipped with WezTerm. I got it to work by commenting out these two lines here