Buy GNU books!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
There are a few predefined variables. The fact that a2ps builds them
at startup changes nothing to their status: they can be modified like
any other variable using
--define (see section 3.1.2 Global Options).
In what follows, there are numbers (i) like this, or (ii) this. It
means that a2ps first tries the solution (i), if a result is obtained
(non empty value), this is the value given to the variable. Otherwise
it tries solution (ii), etc. The rationale behind the order is usually
from user modifiable values (e.g. environment variables) through
system's hard coded values (e.g., calls to
getpwuid) and finally
pw_gecosafter the first `,'), (ii) not defined.
HOME, (ii) the system's database (using
getpwuid), (iii) the empty string.
uname), (ii) the empty string.
LOGNAME, (ii) the environment variable
USERNAME, (iii) the system's database (using
getpwuid), (iv) the translated string `user'.
pw_gecosup to the first `,'), (ii) capitalized value of the variable `user.login' unless it was the translated string `user', (iii) the translated string `Unknown User'.
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|