88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
* the `surf` developers had a couple of options. they
* could have simply broken out the POSIX headers and
* sent the X id to stdout with a call to write(2), the
* correct thing to do. they could have thrown in a call
* to setvbuf(3) to explicitly pick a buffering strategy
* compatible with their usecase, the sensibly wrong
* thing to do. they could have explicitly flushed stdout
* after printf(3)'ing to it, the dumb and error-pront
* thing to do.
*
* instead, they did *nothing.*
*
* so if you run `surf -x` from a terminal, great!
* you'll see it print the x window id first thing.
* you'll then try to capture it via any number of
|
|
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
* the `surf` developers had a couple of options. they
* could have simply broken out the POSIX headers and
* sent the X id to stdout with a call to write(2), the
* correct thing to do. they could have thrown in a call
* to setvbuf(3) to explicitly pick a buffering strategy
* compatible with their usecase, the sensibly wrong
* thing to do. they could have explicitly flushed stdout
* after printf(3)'ing to it, the dumb and error-prone
* thing to do.
*
* instead, they did *nothing.*
*
* so if you run `surf -x` from a terminal, great!
* you'll see it print the x window id first thing.
* you'll then try to capture it via any number of
|