Re: [hackers] [slstatus][PATCH] Handle SIGUSR1 for forced refreshes

2020-11-30 Thread Aaron Marcher
Merged. Thanks! On 20-06-18 Thu, Mart Lubbers wrote: At some point one might want to force a refresh for example after checking email or changing the volume. Sending a SIGUSR1 achieves this now --- slstatus.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/slstatus.c

Re: [hackers] [slstatus][PATCH] Handle SIGUSR1 for forced refreshes

2020-07-16 Thread Mart Lubbers
At some point one might want to force a refresh for example after checking email or changing the volume. Sending a SIGUSR1 achieves this now. --- slstatus.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/slstatus.c b/slstatus.c index 96fa5b6..ee42786 100644 ---

Re: [hackers] [slstatus][PATCH] Handle SIGUSR1 for forced refreshes

2020-07-14 Thread Hiltjo Posthuma
On Tue, Jul 14, 2020 at 02:45:14PM +0200, Mart Lubbers wrote: > Dear all, > I've submitted this patch before but maybe I did something wrong (it was > before > the confirmation mail of the subscription). If there is anything else off with > this email/patch, please let me know. > Best, > >

[hackers] [slstatus][PATCH] Handle SIGUSR1 for forced refreshes

2020-07-14 Thread Mart Lubbers
Dear all, I've submitted this patch before but maybe I did something wrong (it was before the confirmation mail of the subscription). If there is anything else off with this email/patch, please let me know. Best, Original email: At some point one might want to force a refresh for example after

[hackers] [slstatus][PATCH] Handle SIGUSR1 for forced refreshes

2020-06-18 Thread Mart Lubbers
At some point one might want to force a refresh for example after checking email or changing the volume. Sending a SIGUSR1 achieves this now --- slstatus.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/slstatus.c b/slstatus.c index 96fa5b6..499cd30 100644 ---