-
-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some windows don't update their colour scheme when system theme changes #3328
Comments
I can't reproduce this. Are there steps missing from your reproduction instructions? |
This is the config I used for testing: local wezterm = require 'wezterm'
function scheme_for_appearance(appearance)
if appearance:find 'Dark' then
return 'Builtin Solarized Dark'
else
return 'Builtin Solarized Light'
end
end
return {
color_scheme = scheme_for_appearance(wezterm.gui.get_appearance()),
} |
Thank you for looking into it. Surprisingly I cannot replicate it now as well, but just have updated to latest nightly. I wonder if that is because I just restarted Wezterm or there is no issue there no more. I can wait until automatic change at sunset to see if using terminal and having content in windows make any difference. I will keep issue open for now until I conduct bit more investigation, but since we both can't reproduce it right now I understand if you will close it. |
I have managed to trigger the issue. It required few changes between light/dark settings in operating system, switching between workspaces handful of times before colour schemes stopped changing for not current workspace. I know it's very vague and I am not expecting it would push this issue forward, just wanted to update you and perhaps point towards bit more convoluted reproduction required. I will try to see if I can find concise pattern which results in described issue. Appreciate your patience here, thank you! |
Hey Wez, I manage to record a video of an issue. Steps to reproduce:
I have used your configuration from #3328 (comment) to test. I have added some key mappings to ease with changing workspaces, other than that configuration is as in linked response. |
I wonder if this is related to #3685 |
Is there anything you would like me to do to test it further? I am still seeing that issue. |
It might be helpful to capture a session recording of the nvim instance in the affected window.
The file is an asciicast (compatible with https://asciinema.org/) and can also be replayed using The terminal recording allows me to replicate what is being sent to the terminal without requiring me to install the same applications as you and replicate your configuration for everything. |
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. |
note to self: recording was sent via email with subject "wezterm recordings for #3328" |
I can actually reproduce it without neovim. All that's needed on top of configuration from #3328 (comment) (with keymaps to switch between workspaces quickly) local wezterm = require 'wezterm'
function scheme_for_appearance(appearance)
if appearance:find 'Dark' then
return 'Builtin Solarized Dark'
else
return 'Builtin Solarized Light'
end
end
return {
color_scheme = scheme_for_appearance(wezterm.gui.get_appearance()),
keys = {
{ key = 'l', mods = 'CTRL|CMD', action = wezterm.action.SwitchWorkspaceRelative(1) },
{ key = 'h', mods = 'CTRL|CMD', action = wezterm.action.SwitchWorkspaceRelative(-1) },
},
} is
(Please note that you might have to switch between modes handful of times before issue appears.) I am on |
The Issue still persist |
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20230319-202034-51d7b28f
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
Changing colour scheme in response to change in system wide setting does apply changes to single (current) workspace only.
To Reproduce
Observe colour scheme change for active workspace
Observe that new colour scheme didn't get applied here.
Configuration
Expected Behavior
All windows/panes/workspaces to receive updated configuration and change their colour scheme accordingly.
Instead only current workspace gets new colour scheme applied.
Logs
No response
Anything else?
Potentially related to #3259
The text was updated successfully, but these errors were encountered: