You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The steps you took in plain English to reproduce the problem.
In sway config file, putting bar gaps 50 0 has a clear visual effect: the bar is now 50px lower than the top of the screen. Putting it in the config file and reloading sway also has expected effects.
Running swaymsg bar bar-0 gaps 50 0 is well-interpreted by swaymsg and sway (see the log file), but has no visual effect. Running swaymsg -t get_bar_config bar-0 shows the gaps have been updated by sway, but these changes have seemingly not "reached" swaybar, since it doesn't move.
Is it because the swaybar's gaps is given only when swaybar is launched by sway?
The text was updated successfully, but these errors were encountered:
Please fill out the following:
Sway Version:
Debug Log:
Note that I exited using
pkill sway
.Configuration File:
Description:
In sway config file, putting
bar gaps 50 0
has a clear visual effect: the bar is now 50px lower than the top of the screen. Putting it in the config file and reloading sway also has expected effects.Running
swaymsg bar bar-0 gaps 50 0
is well-interpreted by swaymsg and sway (see the log file), but has no visual effect. Runningswaymsg -t get_bar_config bar-0
shows the gaps have been updated by sway, but these changes have seemingly not "reached" swaybar, since it doesn't move.Is it because the swaybar's gaps is given only when swaybar is launched by sway?
The text was updated successfully, but these errors were encountered: