User-specific configuration file for groffer, where
denotes the user's home directory.
This script is called after the system-wide configuration file to
enable overriding by the user.
Their lines either start with a minus character or are shell commands.
Arbitrary spaces are allowed at the beginning, they are just ignored.
The lines with the beginning minus are appended to the existing value
This easily allows to set general
options that are used with any call of
After the transformation of the minus lines the emerging shell scripts
that are called by
using the `
The only option that needs a minus line in the configuration files is
The reason is that its argument must be called at a very early stage
before the whole syntax of the configuration can be transformed.
It makes sense to use these configuration files for the following
Preset command line options by writing them into lines starting with a
Preset environment variables recognized by groffer.
Write a function for calling a viewer program for a special
and feed this name into its corresponding
Note that the name of such a function must coincide with some existing
program in the system path
in order to be recognized by groffer.
As an example, consider the following configuration file in
# groffer configuration file
# groffer options that are used in each call of groffer
--x-viewer='gxditview -geometry 850x800'
# some shell commands
if test "$DISPLAY" = ""; then
This configuration sets four
options and runs two shell commands.
This has the following effects:
Lines starting with a
as the shell to run the
Take a resolution of
and a text color of
in all viewers that support this.
as the X-mode viewer using the geometry option for setting the width
and the height to
is set to
which allows to start
in the standard X display, even when the program is called from a text
Just for fun, the date of each
start is written to the file
in the home directory.