Closed k2662 closed 2 weeks ago
Hello, I'd suggest you to try to disable the code that shows you the os/host/kernel/uptime/.. and see if you still have this issue 🤔
Hello, I'd suggest you to try to disable the code that shows you the os/host/kernel/uptime/.. and see if you still have this issue 🤔
I already tried that.
Does that still reproduce without any config for wezterm? (using wezterm --skip-config
)
If so, please make a recording of the exact output made to the terminal using wezterm record
, and upload the result here for analysis 🙏
yes it still has the % symbol, I cannot seem to get it to record, as it only happens when it takes up the entire screen but not when it is split like this:
it is macos so it uses the .app extension and does not use .desktop files like *bsd or linux. Due to this, it is difficult to use wezterm record.
but here: {"version":2,"width":187,"height":47,"timestamp":1715105109,"command":"'/Applications/WezTerm.app/Contents/MacOS/wezterm --skip-config'","env":{"WEZTERM_TARGET_TRIPLE":"x86_64-apple-darwin", "LANG":"en_US.UTF-8","WEZTERM_VERSION":"20240506-145255-0b50725f"}}
That's zsh marking a partial line (a line that does not end in a newline before a prompt). See PROMPT_EOL_MARK on the zsh manual.
Maybe something is getting a wrong idea of wezterm's width in columns, attempting to move to the next line via outputting spaces, and failing?
My hunch is that the window is being resized/maximized by something outside of wezterm (some local window manager extension?) very early during startup and that is racing with the window size being calculated/observed by your fetch program and zsh.
My hunch is that the window is being resized/maximized by something outside of wezterm (some local window manager extension?) very early during startup and that is racing with the window size being calculated/observed by your fetch program and zsh.
makes sense. I use https://github.com/koekeishiya/yabai as my wm.
I don't have any great suggestions for this; this class of early startup resize issue is a bit thorny to reconcile because, in wezterm, the ptys are started in the context of the multiplexer layer, which may not have a GUI, and the GUI is then notified of the pty and adjusts to render it. Synchronizing the startup/size with that is technically possible with some effort, but it would come at the cost of introducing some additional delay during startup which many users will not tolerate.
In the meantime, if it really bothers you, then you could try:
or you can tell zsh not to show this mark: https://superuser.com/questions/645599/why-is-a-percent-sign-appearing-before-each-prompt-on-zsh-in-windows
What Operating System(s) are you seeing this problem on?
macOS
Screenshot of issue:
WezTerm version
20240203-110809-5046fc22 and 20240506-145255-0b50725f
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
a % symbol always shows at startup
To Reproduce
set zsh PS1 to PS1='%F{green}%1~>%f '
Configuration
My Theme
Expected Behavior
There shouldn't be random % symbol at startup. kitty terminal doesn't have this issue
Logs
10:05:29.412 INFO wezterm_gui::termwindow > QuitApplication over here (window)
Anything else?
No response