-
-
Notifications
You must be signed in to change notification settings - Fork 723
Description
Describe the issue
Actual behavior:
A clear and concise description of what the bug is.
module/bspwm still create a separator for every workspaces even for those that have an empty label. Here's an excerpt of my config file. This behavior create an unwanted gap between workspaces' labels.
Expected behavior:
A clear and concise description of what you expected to happen.
module/bspwm shouldn't create a separator for empty workspaces when label-empty is set to nothing.
Was it working before?
- Did you also experience this bug in an earlier version of polybar?
- If no, what was the last version where this worked correctly?
I wasn't using bspwm prior to the version of polybar I'm actually using.
To Reproduce
A minimal but complete config with which the problem occurs:
- add those settings:
label-empty =
label-focused = %name%
label-occupied = %name%
label-separator = " "- Open an application on workspace 1
- Move to workspace 3 or greater
List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.
Polybar Log
Post everything polybar outputs to the terminal when you run it and the issue occurs below
There's no error in the output.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
- WM: bspwm
- Output of
polybar -vvv:
polybar 3.2.1
Features: -alsa -curl +i3 -mpd +network +pulseaudio +xkeyboard
X extensions: +randr (+monitors) -render -damage -sync -composite +xkb +xrm +xcursor
Build type: RelWithDebInfo
Compiler: /usr/bin/clang++
Compiler flags: -Wall -Wextra -Werror -O2 -pedantic -pedantic-errors -Wno-error=parentheses-equality -Wno-zero-length-array
Linker flags:
Additional context
Add any other context that you think is necessary about the problem here.
As a temporary workaround, I've removed label-separator and adeed an Em Space (U+2003) in front of %name% in label-focused and label-occupied to simulate a separator on those two labels.