Two steps: First, expand tabs to 8 spaces in code and structure
listings. Second, make the .Ds used to wrap code listings switch to
constant-width font (CW) rather than numeric font position 1, which
maps to R on most systems.
It is possible some archaic systems won't know what CW is, but the
only risk is that code listings won't look quite right on troff
devices; the PostScript and DVI drivers definitely grok it, so those
important cases are OK.
The purpose of these changes is to get rid of presentation-level
markup so these pages will lift clean to DocBook.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
This man page does not discuss the actual return values of the
function, but says they are of type "Status". One might assume
that this means you could compare it with the "Success" macro.
One would be wrong.
The X functions seem to have two three types representing status.
If it is an "int" there are a number of error codes or "Success"
which can be compared against. If it is a bool, the result can be
compared with "True" or "False". If the return type is "Status" it
appears that the return type is either 0 or 1. Unfortunately the
value for Success is zero, so it is important to distinguish
between the first two types of return values and the third;
otherwise the conditional will be inverted.
XGetWindowAttributes() is one of the functions which returns zero
for failure. The man page should make this clear.
