[SOLVED] dwmblocks script error

charbelsako · 11-05-2020, 12:09 PM

I recently got dwmblocks and wrote 2 scripts for volume and brightness but I can't see the values in the status bar.

Here are the scripts
volume:
-------

Code:

<script type="bash">
#! /bin/bash
echo "hello"
exit

case $BLOCK_BUTTON in
	1) pactl set-sink-mute 0 toggle
esac

vol=$(pactl list sinks | grep '^[[:space:]]Volume:' | sed -e 's,.* \([0-9][0-9]*\)%.*,\1,')
printf "%s%%" "$vol"
</script>

brightness:
-----------

Code:

<script type="bash">
#! /bin/bash

brightness=$(xbacklight -get)

printf "%i%%" "$brightness"
</script>

the files work by themselves but don't show up in dwmblocks. I have also added the files' location to the PATH variable

Finally here's my blocks.h file
blocks.h:
---------

Code:

//Modify this file to change what commands output to your statusbar, and recompile using the make command.
static const Block blocks[] = {
	/*Icon*/	/*Command*/		/*Update Interval*/	/*Update Signal*/
	{"Mem:", "free -h | awk '/^Mem/ { print $3"/"$2 }' | sed s/i//g",	30,		0},

	{"", "date '+%a %b %d %I:%M%p'",					5,		0},
	{"VOL:", "volume", 							1,  		0},
	{"Brightness: ", "brightness", 						5, 		0}
};

//sets delimeter between status commands. NULL character ('\0') means no delimeter.
static char delim[] = " | ";
static unsigned int delimLen = 5;

I also would like to know what values should I set for updateinterval and updatesignal as there is no documentation for them

If you want more info I do have an image of my status bar. Just tell me where i can upload it?

individual · 11-05-2020, 04:38 PM

Have you tried hard-coding the path to those files, e.g., /home/user/bin/volume? It looks like update interval is calculated as seconds. So your mem command be called every 30 seconds. The signal option looks like it accepts a standard UNIX signal to determine when to call the command. Type man 7 signal in your terminal to see all the signals.

chrism01 · 11-05-2020, 10:27 PM

1.please use code blocks https://www.linuxquestions.org/quest...do=bbcode#code

2.

Code:

volume:
-------
#! /bin/bash
echo "hello"
exit

So script exits (almost) immediately

charbelsako · 11-06-2020, 12:32 AM

Quote:

Originally Posted by individual

Have you tried hard-coding the path to those files, e.g., /home/user/bin/volume? It looks like update interval is calculated as seconds. So your mem command be called every 30 seconds. The signal option looks like it accepts a standard UNIX signal to determine when to call the command. Type man 7 signal in your terminal to see all the signals.

This works

charbelsako · 11-06-2020, 12:38 AM

Quote:

Originally Posted by individual

Have you tried hard-coding the path to those files, e.g., /home/user/bin/volume? It looks like update interval is calculated as seconds. So your mem command be called every 30 seconds. The signal option looks like it accepts a standard UNIX signal to determine when to call the command. Type man 7 signal in your terminal to see all the signals.

How would I make It update immediately after I press the button?

ondoho · 11-06-2020, 01:06 AM

Quote:

Originally Posted by charbelsako

How would I make It update immediately after I press the button?

A button on your dwm bar?
By coding the wanted behavior in C.
Probably goes beyond editing the .h file.

charbelsako · 11-06-2020, 11:13 AM

Quote:

Originally Posted by ondoho

A button on your dwm bar?
By coding the wanted behavior in C.
Probably goes beyond editing the .h file.

I mean how would I make it update after I press the raise volume button on my keyboard. Right now it updates every second

ondoho · 11-06-2020, 02:30 PM

What's the "Update Signal" registered in blocks.h?
You send that signal to the blocks application, probably with the 'kill' command. 'man kill'.
Once you got that working, bind it to a hotkey (which involves editing dwm's own .h file if memory serves).

charbelsako · 11-10-2020, 06:40 AM

Quote:

Originally Posted by ondoho

What's the "Update Signal" registered in blocks.h?
You send that signal to the blocks application, probably with the 'kill' command. 'man kill'.
Once you got that working, bind it to a hotkey (which involves editing dwm's own .h file if memory serves).

It works

ondoho · 11-10-2020, 02:07 PM

Quote:

Originally Posted by charbelsako

It works

Mark SOLVED please