vivien / i3blocks

The hacker-friendly status_command for Sway and i3
https://vivien.github.io/i3blocks/
GNU General Public License v3.0
2.28k stars 181 forks source link

Separator setting not respecting non-rendered blocks #439

Open allgreed opened 3 years ago

allgreed commented 3 years ago

My situation:

I have 2 blocks side-by-side one is rendering, the other is not [they're memory indicators - one showing RAM and the other swap and I don't have any swap on the current machine].

Relevant config:

[memory]
label= 
command=~/.scripts/blocks/memory
interval=15
separator=false

[memory]
label= SWAP
instance=swap
command=~/.scripts/blocks/memory
interval=15

[any block really]
# but in my case it's disk

I'd like this to happen:

2020-10-24-01-35-25_263x32 Because the separator is false on memory it should apply to the non-rendered swap

But this happens:

2020-10-24-01-35-47_292x43

Potential workarounds

Questions

vivien commented 1 year ago

Unfortunately this is a limitation of the i3bar protocol which draws the separator after the block. You may draw an arbitrary separator with a static block like this (full_text is a space) after your swap block:

[separator]
full_text= 
separator=true

There is also a more complex example in the FAQ.

vivien commented 1 year ago

Supporting multi blocks output is something I'm evaluating, but still worried that it would bring more complexity than value I must say.