Closed oOosys closed 4 months ago
Is this a login shell vs. non-login shell issue? Try launching as a non-login shell https://wezfurlong.org/wezterm/config/launch.html#launching-programs
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
Linux X11
Which Wayland compositor or X11 Window manager(s) are you using?
xfwm4
WezTerm version
wezterm 20240203-110809-5046fc22
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
No, and I'll explain why below
Describe the bug
dash prompt in wezterm if started with dash as default shell:
\t \w $
dash prompt in wezterm if dash run from bash:\[\e]0;\u@\h: \w\a\]\[\033[01;32m\]~ $ \[\033[00m\]
dash prompt in xfce4-terminal and any other terminals:$
Why not nightly? I am on volume limited Internet connection, only extremely rare using dash and one of my guidelines is 'never change an already tested running system".
To Reproduce
Start wezterm with bash as default shell and then run the command:
~ $ dash
Configuration
Expected Behavior
I expect wezterm to behave similar to all the other terminals available on my system:
Logs
No response
Anything else?
No response