8210c6be79
i3bar: Allow child to specify signals to use
...
We now wait for the child process to send the first line before stopping
it to use the signal which might be specified in the i3bar protocol
header
Since clients might use the same signal for both stop and cont, we also
save the stopped state of the child to avoid stopping it while hidden!
2012-09-22 15:13:21 +02:00
34dc6d4d64
i3bar: Introduce i3bar_child struct
2012-09-22 15:13:21 +02:00
b9255f51f8
Use (void) instead of () for functions without args
2012-08-23 19:34:37 +02:00
d519659ea7
i3bar: kill child processes when exit()ing (they might be stopped) (Thanks darkraven)
2012-03-26 17:36:00 +02:00
726f2a1e5a
normalize file headers across **/*.{h,c}
2011-10-25 21:19:38 +01:00
8d09ed7bf5
Update changelog and copyright, bump version and more
2011-07-31 16:16:17 +02:00
a83e7699e7
Send the child SIGSTOPs and SIGCONTs
2010-08-25 18:31:03 +02:00
60da522e13
Add licensing information
2010-08-07 18:05:16 +02:00
cee972280d
Add comments
2010-08-07 02:10:05 +02:00
7d7867acce
Be more strict with encapsulation
...
I.e. move the xcb-event-handling into xcb.c and the
child-process-communications into newly created child.c.
Also change some includes.
2010-08-05 05:09:59 +02:00
Quentin Glidic