Use 'pgrep -o' instead of 'pidof -s' to get the PID of status bar

[UtkarshVerma]

This is being done to extend compatibility to dwmblocks-async which creates a subprocess, because of which pidof -s dwmblocks returns the PID of the subprocess, instead of the parent, which handles the signals.

Without this PR, dwmblocks-async doesn't get click events.

Below is a quick comparison of both commands. The PID of the parent is 21677.

❯ pidof dwmblocks
21678 21677
❯ pgrep dwmblocks
21677
21678
❯ pidof -s dwmblocks
21678
❯ pgrep -o dwmblocks
21677

[bakkeby]

This would break for anyone not using your version of dwmblocks though.

[UtkarshVerma]

No, it's backwards compatible.
pidof -s just gets the PID of the latest instance of dwmblocks. As long as only one instance of dwmblocks is running, pgrep -o does the same job.

[bakkeby]

Yes that should be fine then. Even if you were have more than one instance of dwmblocks running then using pidof wouldn't reliably give you the right instance either.

[UtkarshVerma]

@bakkeby could you please label this PR as 'hacktoberfest-accepted'?

[bakkeby]

Done.