Skip to content
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

Issue when using second subscribe #55

Open
RestlessLizard opened this issue Apr 6, 2021 · 8 comments
Open

Issue when using second subscribe #55

RestlessLizard opened this issue Apr 6, 2021 · 8 comments

Comments

@RestlessLizard
Copy link

Here is my config. If I enable [volume] block my desktop block will hand and not update at all after initial render

[bar]
name = "testbar"
blocks = "desktop | | volume ram cpu datetime "
height = 30
foreground = "#fff"
background = "#222"
font = "Hack Nerd Font"

separator = "|"
#areas = 16

[default]
label-foreground = "#fff"
affix-foreground = "#555555"
margin = 8

[desktop]
command = "~/scripts/bar/workspaces.sh"
trigger = "bspc subscribe desktop_focus"
margin-left = 16
raw = true

[datetime]
command = "date +'%T %a %F'"
interval = 1
margin-right = 16

[cpu]
label = "CPU "
command = "~/scripts/bar/cpu.sh"
interval = 3

[ram]
label = "RAM "
command = "~/scripts/bar/ram.sh"
interval = 3

[volume]
label = "VOL "
trigger = "pactl subscribe"
command = "~/scripts/bar/vol.sh"
@RestlessLizard
Copy link
Author

Also, this issue happens if I try to use another bspc subscribe

@domsson
Copy link
Owner

domsson commented Apr 6, 2021

Thank you very much for reporting this! I'll look into it and will let you know once I figure out what's going on.

While I'm trying to sort this out, here is a possible workaround: you could use a volume script that doesn't require a trigger and instead keeps printing the volume whenever it changes. I've written one myself, but a quick search also brings up this one. Then you could remove trigger and instead put live = true.

@RestlessLizard
Copy link
Author

Wow, thanks for quick response! I love succade so much, props to you buddy!

@domsson
Copy link
Owner

domsson commented Jun 28, 2021

Only little time recently, just started looking into it now. Haven't figured it out yet, but one interesting finding:

  • Can reproduce if I put the bspc block FIRST, then the pactl block
  • Issue does not present if the order of the blocks is reversed, however

@midirhee12
Copy link

midirhee12 commented Nov 9, 2021

I have the same issue with multiple bspc subscribes. And putting a block before the desktop block does not change behavior in the case of multiple subscribes.

@midirhee12
Copy link

midirhee12 commented Nov 9, 2021

Update: Found some interesting behavior:

[bar]
name = "bar0"
blocks = "foo desktops test | test foo baz | cpu memory datetime"
height = 24
areas = 16
foreground = "#eeeeee"
background = "#00000000"
line-color ="#081e35"
line-width = 2

[default]
label-foreground = "#dddddd"
background = "#88000000"
affix-foreground = "#555555"
margin = 8
padding-left = 1
padding-right = 1
underline = true

[test]
command = "echo test"
trigger = "bsp subscribe"

[foo]
command = "echo foo"
trigger = "bsp subscribe"

[baz]
command = "echo baz"
trigger = "bsp subscribe"

[desktops]
command = "~/.config/succade/desktops.sh"
trigger = "bspc subscribe desktop_focus"
raw = true

[cpu]
command = "~/.config/succade/cpu.sh"
interval = 1
mouse-left = "~/.config/succade/cpups.sh"
mouse-right = "~/.config/succade/cputemp.sh"

[memory]
command = "~/.config/succade/memory.sh"
interval - 1
mouse-left = "~/.config/succade/memoryps.sh"

[datetime]
command = "date +'%y-%m-%d %H:%M'"
interval = 1
margin-right = 8

Not sure if completely related. But I think this expands upon this issue in some way

@midirhee12
Copy link

After a reboot, succaderc deleted itself.

@midirhee12
Copy link

Don't expect me to provide further information. I might be switching b/c this is just ridiculous which I think you can understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants