-
Notifications
You must be signed in to change notification settings - Fork 181
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
problem with current version #44
Comments
Hi @xelite, If you |
$ i3blocks -c /home/xelite/.i3/.i3blocks-left-monitor.conf |
So it seems to use the correct file. I tried the following i3 conf:
And it works properly. What were you expecting exactly? |
i3block is using good file but not show all sections from config. Look at screenshots below: My config:
When I am using current version I don't have some sections and I don't have idea why? |
After move old binary and restart wm i3blocks looks property. |
Looking at the screenshot and the config, the only missing block is dunst, but you may have no notification. With the current version, stderr is caught and written to i3blocks debug output. Can you:
and look for
The general debug output should give you a good clue about what's going on. |
I also don't have volume block. Debug says (at every refresh):
About dunst, you have right. If doesn't have notification, it will be show nothing. But volume's script have always output:
My volume script:
|
ho ok. Since ede5851, if no interval is specified, the block won't be executed. This was introduced to easily make "buttons" (click-only commands). For a block such as the volume, you have to add In the meantime, feel free to update the wiki with your script, the button switch case is nice! |
Also, since 6712002 I switched to real-time signals, so if you specify |
I corrected config and now everything works properly. Thanks a lot for support. I created pull request with updated volume's script. After merge I'll update wiki. Cheers. |
Current version doesn't read property my configs from arg -c (i have 2 configs for 2 monitors). When I back to 1.2-19-gb6d98be everything works with the same configuration.
The text was updated successfully, but these errors were encountered: