1 .TH GROFF_TMAC @MAN5EXT@ "@MDATE@" "Groff Version @VERSION@"
3 groff_tmac \- macro files in the roff typesetting system
5 .\" The .SH was moved to this place to make `apropos' happy.
8 .\" --------------------------------------------------------------------
10 .\" --------------------------------------------------------------------
15 File position: <groff-source>/man/groff_tmac.man
17 Last update: 16 Nov 2006
19 This file is part of groff, the GNU roff type-setting system.
21 Copyright (C) 2000, 2001, 2002, 2003, 2004, 2006
22 Free Software Foundation, Inc.
23 written by Bernd Warken <bwarken@mayn.de> and Werner Lemberg
26 Permission is granted to copy, distribute and/or modify this document
27 under the terms of the GNU Free Documentation License, Version 1.1 or
28 any later version published by the Free Software Foundation; with the
29 Invariant Sections being this .ig-section and AUTHOR, with no
30 Front-Cover Texts, and with no Back-Cover Texts.
32 A copy of the Free Documentation License is included as a file called
33 FDL in the main directory of the groff source package.
36 .\" --------------------------------------------------------------------
38 .\" --------------------------------------------------------------------
40 .do nr groff_tmac_C \n[.C]
52 .ds Ellipsis \&.\|.\|.\&\"
54 .\" Global static variables for inter-macro communication
57 .\" --------------------------------------------------------------------
58 .\" setup for the macro definitions below
60 .\" naming: namespace:cathegory_macro.variable_name (experimental)
62 .\" --------------------------------------------------------------------
63 .\" configuration of prompt for `.Shell_cmd'* macros
64 .ds groffer:Shell_cmd.prompt_text sh#\" prompt for shell commands
65 .ds groffer:Shell_cmd+.prompt_text >\" prompt on continuation lines
66 .ds groffer:Shell_cmd_base.prompt_font I\" font for prompts
68 .\" automatically determine setup from the configuration above
69 .als @f groffer:Shell_cmd_base.prompt_font\"
70 .als @t groffer:Shell_cmd.prompt_text\"
71 .als @t+ groffer:Shell_cmd+.prompt_text\"
72 .ds groffer:Shell_cmd.prompt \f[\*[@f]]\*[@t]\f[]\" needed
73 .ds groffer:Shell_cmd+.prompt \f[\*[@f]]\*[@t+]\f[]\" needed
74 .nr @w \w'\*[groffer:Shell_cmd.prompt]'\"
75 .nr @w+ \w'\*[groffer:Shell_cmd+.prompt]'\"
77 .\" Full prompt width is maximum of texts plus 1m
78 .nr groffer:Shell_cmd_base.prompt_width (\n[@w]>?\n[@w+]+1m)\" needed
87 .\"--------------------------------------------------------------------
88 .\" Ignore all arguments like a comment, even after a .eo call.
91 .c --------------------------------------------------------------------
96 . ds @tmp@ \fB\\$1\f[]\fI\\$2\f[]
98 . Text \\*[@tmp@]\fR\\$*\f[]
102 .c --------------------------------------------------------------------
103 .c .Env_var (<env_var_name> [<punct>])
105 .c Display an environment variable, with optional punctuation.
110 . Text \f[CB]\\$1\f[]\\$2
113 .c --------------------------------------------------------------------
114 .c .Error (<text>...)
116 .c Print error message to terminal and abort.
122 .c --------------------------------------------------------------------
124 . if r@+Example_font \
125 . Error previous .Example was not terminated by a ./Example
126 . nr @+Example_font \\n[.f]
132 .c --------------------------------------------------------------------
134 . if !r@+Example_font \
135 . Error no previous call to .Example
136 . ft \\n[@+Example_font]
143 .c --------------------------------------------------------------------
144 .c .Shell_cmd (<CR> [<CI>] ...)
146 .c A shell command line; display args alternating in fonts CR and CI.
149 .c .Shell_cmd "groffer --dpi 100 file"
150 .c result: `sh# groffer --dpi 100 file'
151 .c with 'sh#' in font I, the rest in CR
153 .c .Shell_cmd groffer\ --dpi\ 100\ file
154 .c result: the same as above
156 .c .Shell_cmd "groffer --dpi=" value " file"
157 .c result: sh# groffer --dpi=value file
158 .c with `groffer --dpi=' and `file' in CR; `value' in CI
160 .c .Shell_cmd groffer\ --dpi= value \ file
161 .c result: the same as the previous example
164 . groffer:Shell_cmd_base "\*[groffer:Shell_cmd.prompt]" \\$@
166 .c --------------------------------------------------------------------
167 .c .Shell_cmd+ (<CR> [<CI>] ...)
169 .c A continuation line for .Shell_cmd.
172 . groffer:Shell_cmd_base "\*[groffer:Shell_cmd+.prompt]" \\$@
174 .c --------------------------------------------------------------------
175 .c .Shell_cmd_base (<prompt> [<CR> [<CI>] ...])
177 .c A shell command line; display args alternating in fonts CR and CI.
178 .c Internal, do not use directly.
180 .c Globals: read-only register @.Shell_cmd_width
182 .de groffer:Shell_cmd_base
183 . if (\\n[.$] <= 0) \
185 . nr @+font \\n[.f]\"
188 . c gap between prompt and command
189 . nr @+gap \\n[groffer:Shell_cmd_base.prompt_width]-\\w'\\*[@prompt]'\"
190 . ds @res \\*[@prompt]\h'\\n[@+gap]u'\"
193 . while (\\n[.$] > 0) \{\
194 . as @res \\f[\\*[@cf]]\\$1\"
216 .c --------------------------------------------------------------------
219 .c Treat the arguments as text, no matter how they look.
222 . if (\\n[.$] == 0) \
226 .c --------------------------------------------------------------------
227 .c .Topic ([<indent>])
229 .c A bulleted paragraph
240 .c --------------------------------------------------------------------
243 .c Continuation line for .TP header.
250 .c --------------------------------------------------------------------
252 . ds @tmp@ `\f(CR\\$1\f[]'
254 . Text \\*[@tmp@]\\$*
257 .c --------------------------------------------------------------------
259 . ds @tmp@ \f(CB\\$1\f[]
261 . Text \\*[@tmp@]\\$*
264 .c --------------------------------------------------------------------
266 . ds @tmp@ \f(CI\\$1\f[]
268 . Text \\*[@tmp@]\\$*
271 .c --------------------------------------------------------------------
273 . ds @tmp@ \f(CB\\$1\f[]
275 . Text .\\*[@tmp@]\\$*
278 .c --------------------------------------------------------------------
280 . ds @tmp@ \f[CB]\\$1\f[]
282 . Text \[rs]\\*[@tmp@]\\$*
285 .\" --------------------------------------------------------------------
287 .\" --------------------------------------------------------------------
291 type-setting system provides a set of macro packages suitable for
292 special kinds of documents.
294 Each macro package stores its macros and definitions in a file called
297 The name is deduced from
303 The tmac files are normal roff source documents, except that they
304 usually contain only definitions and setup commands, but no text.
306 All tmac files are kept in a single or a small number of directories,
312 .\" --------------------------------------------------------------------
313 .SH "GROFF MACRO PACKAGES"
314 .\" --------------------------------------------------------------------
317 provides all classical macro packages, some more full packages, and
318 some secondary packages for special purposes.
320 Note that it is not possible to use multiple primary macro packages at the
321 same time; saying e.g.\&
324 .Shell_cmd "groff \-m man \-m ms foo"
330 .Shell_cmd "groff \-m man foo \-m ms bar"
336 .\" --------------------------------------------------------------------
338 .\" --------------------------------------------------------------------
342 This is the classical macro package for UNIX manual pages
343 (man\~pages); it is quite handy and easy to use; see
344 .BR groff_man (@MAN7EXT@).
351 An alternative macro package for man\~pages mainly used in BSD
352 systems; it provides many new features, but it is not the standard for
354 .BR groff_mdoc (@MAN7EXT@).
357 .\" --------------------------------------------------------------------
359 .\" --------------------------------------------------------------------
361 The packages in this section provide a complete set of macros for
362 writing documents of any kind, up to whole books.
364 They are similar in functionality; it is a matter of taste which one
373 .BR groff_me (@MAN7EXT@).
381 .BR groff_mm (@MAN7EXT@).
388 macro package, only available in groff.
390 As this is not based on other packages, it can be freely designed.
392 So it is expected to become quite a nice, modern macro package.
395 .BR groff_mom (@MAN7EXT@).
403 .BR groff_ms (@MAN7EXT@).
406 .\" --------------------------------------------------------------------
407 .SS "Language-specific Packages"
408 .\" --------------------------------------------------------------------
413 This file adds support for French localization of the main macro packages
414 (me, mom, mm, and ms).
420 .Shell_cmd "groff -ms -mfr foo.ms > foo.ps"
426 sets the input encoding to latin-9 to get proper support of the `oe'
432 Swedish localization support for the me, mom, and ms macro packages.
434 Note that Swedish for the mm macros is handled separately; see
435 .BR groff_mmse (@MAN7EXT@).
437 It should be used as the last macro package on the command line.
440 .\" --------------------------------------------------------------------
441 .SS "Input Encodings"
442 .\" --------------------------------------------------------------------
453 Various input encodings supported directly by groff.
455 Normally, this macro is loaded at the very beginning of a document or
456 specified as the first macro argument on the command line.
459 loads latin1 by default at start-up.
461 Note that these macro packages don't work on EBCDIC hosts.
466 Encoding support for EBCDIC.
468 On those platforms it is loaded automatically at start-up.
470 Due to different character ranges used in
472 it doesn't work on architectures which are based on ASCII.
476 Note that it can happen that some input encoding characters are not
477 available for a particular output device.
483 . Text groff -Tlatin1 -mlatin9 ...
487 fails if you use the Euro character in the input.
489 Usually, this limitation is present only for devices which have a
490 limited set of output glyphs
493 for other devices it is usually sufficient to install proper
494 fonts which contain the necessary glyphs.
497 .\" --------------------------------------------------------------------
498 .SS "Special Packages"
499 .\" --------------------------------------------------------------------
501 The macro packages in this section are not intended for stand-alone
502 usage, but can be used to add special functionality to any other
503 macro package or to plain groff.
508 Provide some macros for addition, multiplication, and division of 60bit
509 integers (allowing safe multiplication of 30bit integers, for example).
514 Switch to the EC and TC font families. To be used with
515 .BR \%grodvi (@MAN1EXT@)
516 \[en] this man page also gives more details how to use it.
521 This macro file is already loaded at start-up by
523 so it isn't necessary to call it explicitly.
525 It provides an interface to set the paper size on the command line with
526 the option \f[B]\%\-dpaper=\f[]\f[I]size\f[].
530 are the same as the predefined
532 values in the DESC file (only lowercase; see
533 .BR groff_font (@MAN5EXT@)
539 (ell) character denotes landscape orientation.
547 Most output drivers need additional command line switches
551 to override the default paper length and orientation as set in the driver
554 For example, use the following for PS output on A4 paper in landscape
558 .Shell_cmd "groff \-Tps \-dpaper=a4l \-P\-pa4 \-P\-l \-ms foo.ms > foo.ps"
563 This file provides proper definitions for the macros
568 .BR @g@pic (@MAN1EXT@)
571 They center each picture.
573 Use it only if your macro package doesn't provide proper definitions
574 for those two macros (actually, most of them already have).
579 A single macro is provided in this file,
581 to include a PostScript graphic in a document.
583 The following output devices support inclusion of PS images:
588 for all other devices the image is replaced with a hollow rectangle
591 This macro file is already loaded at start-up by
593 so it isn't necessary to call it explicitly.
599 \&\fB.PSPIC\fP [\fB\-L\fP\||\|\fB-R\fP\||\|\fB\-I\fP\ \fIn\fP] \
600 \fI\|file\fP [\fIwidth\fP [\fIheight\fP]]
605 is the name of the PostScript file;
609 give the desired width and height of the image.
615 argument is specified, the image's natural width (as given in
616 the file's bounding box) or the current line length is used
617 as the width, whatever is smaller.
623 arguments may have scaling indicators attached;
624 the default scaling indicator is\~\c
627 This macro scales the graphic uniformly
628 in the x and y\~directions so that it is no more than
635 By default, the graphic is horizontally centered.
641 options cause the graphic to be left-aligned and right-aligned,
646 option causes the graphic to be indented by\~\c
648 (default scaling indicator is\~\c
654 within a diversion it is recommended to extend it with
655 the following code, assuring that the diversion's width completely
656 covers the image's width.
663 . Text \[rs]h'(\[rs]\[rs]n[ps-offset]u + \[rs]\[rs]n[ps-deswid]u)'
673 Use this for tracing macro calls.
675 It is only useful for debugging.
678 .BR groff_trace (@MAN7EXT@) .
683 Overrides the definition of standard troff characters and some groff
684 characters for tty devices.
686 The optical appearance is intentionally inferior compared to that of
687 normal tty formatting to allow processing with critical equipment.
692 Additions of elements known from the html format, as being used in the
693 internet (World Wide Web) pages; this includes URL links and mail
695 .BR groff_www (@MAN7EXT@).
698 .\" --------------------------------------------------------------------
700 .\" --------------------------------------------------------------------
702 In classical roff systems, there was a funny naming scheme for macro
703 packages, due to a simplistic design in option parsing.
705 Macro packages were always included by option
707 when this option was directly followed by its argument without an
708 intervening space, this looked like a long option preceded by a single
709 minus \[em] a sensation in the computer stone age.
711 To make this optically working for macro package names, all classical
712 macro packages choose a name that started with the letter
714 which was omitted in the naming of the macro file.
718 For example, the macro package for the man pages was called
722 So it could be activated by the argument
732 For similar reasons, macro packages that did not start with an
736 added in the documentation and in talking; for example, the package
741 in the documentation, although a more suitable name would be
743 For, when omitting the space between the option and its argument, the
744 command line option for activating this package reads
749 To cope with all situations, actual versions of
750 .BR groff (@MAN1EXT@)
751 are smart about both naming schemes by providing two macro files
752 for the inflicted macro packages; one with a leading
754 the other one without it.
760 macro package may be specified as on of the following four methods:
763 .Shell_cmd "groff\ \-m\ man"
764 .Shell_cmd "groff\ \-man"
765 .Shell_cmd "groff\ \-mman"
766 .Shell_cmd "groff\ \-m\ an"
770 Recent packages that do not start with
772 do not use an additional
774 in the documentation.
778 macro package may be specified only as one of the two methods:
781 .Shell_cmd "groff\ \-m\ www"
782 .Shell_cmd "groff\ \-mwww"
786 Obviously, variants like
788 would not make much sense.
792 A second strange feature of classical troff was to name macro files
795 In modern operating systems, the type of a file is specified as
796 postfix, the file name extension.
798 Again, groff copes with this situation by searching both
808 The easiest way to find out which macro packages are available on a
809 system is to check the man\~page
810 .BR groff (@MAN1EXT@),
811 or the contents of the
819 most macro packages are described in\~man pages called
820 .BR groff_\f[I]name\f[] (@MAN7EXT@),
823 for the classical packages.
826 .\" --------------------------------------------------------------------
828 .\" --------------------------------------------------------------------
830 There are several ways to use a macro package in a document.
832 The classical way is to specify the troff/groff option
835 at run-time; this makes the contents of the macro package
841 is searched within the tmac path; if not found,
843 is searched for instead.
847 Alternatively, it is also possible to include a macro file by adding
851 into the document; the argument must be the full file name of an
852 existing file, possibly with the directory where it is kept.
854 In groff, this was improved by the similar request
857 which added searching in the tmac path, just like option
863 Note that in order to resolve the
867 requests, the roff preprocessor
868 .BR soelim (@MAN1EXT@)
869 must be called if the files to be included need preprocessing.
871 This can be done either directly by a pipeline on the command line or
872 by using the troff/groff option
876 calls soelim automatically.
880 For example, suppose a macro file is stored as
881 .I @MACRODIR@/macros.tmac
882 and is used in some document called
887 At run-time, the formatter call for this is
890 .Shell_cmd "groff\ \-m\ " "macrofile\ document.roff"
894 To include the macro file directly in the document either
898 . Text .mso macrofile.tmac
906 . Text .so @MACRODIR@/macros.tmac
911 In both cases, the formatter is called with
913 .Shell_cmd "groff\ \-s\ " docu.roff
917 If you want to write your own groff macro file, call it
919 and put it in some directory of the tmac path, see section
921 Then documents can include it with the
923 request or the option
928 .\" --------------------------------------------------------------------
930 .\" --------------------------------------------------------------------
932 .\" This section does not fit into the framework of this document.
934 There is a convention that is supported by many modern roff
939 described in the following.
942 If the first line in a document is a comment, the first word (after the
943 comment characters and a blank) constitutes the
946 That means that the letters of this word are interpreted as
947 abbreviations for those preprocessor commands that should be run
948 when formatting the document.
950 Mostly, only the letters corresponding to the options for the
951 preprocessors are recognized,
971 .BR roff (@MAN7EXT@)).
975 Besides being a good reminder for the user, some formatters (like the
977 program) are even able to automatically start the preprocessors
978 specified in the preprocessor word, but do not bet on this.
984 program handles some preprocessors automatically, such that in
985 man\~pages only the following characters should be used:
993 .\" --------------------------------------------------------------------
995 .\" --------------------------------------------------------------------
999 document is a text file that is enriched by predefined formatting
1000 constructs, such as requests, escape sequences, strings, numeric
1001 registers, and macros from a macro package.
1003 These elements are described in
1004 .BR roff (@MAN7EXT@).
1008 To give a document a personal style, it is most useful to extend the
1009 existing elements by defining some macros for repeating tasks; the best
1010 place for this is near the beginning of the document or in a separate
1015 Macros without arguments are just like strings.
1017 But the full power of macros reveals when arguments are passed with a
1020 Within the macro definition, the arguments are available as the escape
1025 .BR $[ \*[Ellipsis] ] ,
1029 the name under which the macro was called is in
1031 and the number of arguments is in register
1034 .BR groff (@MAN7EXT@).
1037 .\" --------------------------------------------------------------------
1039 .\" --------------------------------------------------------------------
1041 The phase when groff reads a macro is called
1045 This is comparable to the C\~preprocessing phase during the development
1046 of a program written in the C\~language.
1050 In this phase, groff interprets all backslashes; that means that all
1051 escape sequences in the macro body are interpreted and replaced by
1054 For constant expression, this is wanted, but strings and registers
1055 that might change between calls of the macro must be protected from
1058 This is most easily done by doubling the backslash that introduces the
1061 This doubling is most important for the positional parameters.
1063 For example, to print information on the arguments that were passed to
1064 the macro to the terminal, define a macro named `.print_args',
1069 .ds @1 \[rs]f[I]\[rs]\[rs]$0\[rs]f[]\"
1072 . Text .ds midpart was called with
1073 . Text .de print_args
1074 . Text .\ \ tm\ \*[@1]\ \[rs]\[rs]*[midpart]\ \[rs]\[rs]n[.$]\ \*[@2]
1075 . Text .\ \ tm\ \[rs]\[rs]$*
1083 When calling this macro by
1087 . Text .print_args arg1 arg2
1091 the following text is printed to the terminal:
1095 . Text \f[CI]print_args\f[] was called with the following 2 arguments:
1101 Let's analyze each backslash in the macro definition.
1103 As the positional parameters and the number of arguments change
1104 with each call of the macro their leading backslash must be doubled,
1108 .IR \[rs]\[rs][.$] .
1109 The same applies to the macro name because it could be called with an
1117 is a constant string, it does not change, so no doubling for
1118 .IR \[rs]*[midpart] .
1121 escape sequences are predefined groff elements for setting the font
1124 Of course, this behavior does not change, so no doubling with
1130 .\" --------------------------------------------------------------------
1132 .\" --------------------------------------------------------------------
1134 Writing groff macros is easy when the escaping mechanism is temporarily
1137 In groff, this is done by enclosing the macro definition(s) into a
1144 Then the body in the macro definition is just like a normal part of
1145 the document \[em] text enhanced by calls of requests, macros,
1146 strings, registers, etc.
1148 For example, the code above can be written in a simpler way by
1152 .ds @1 \[rs]f[I]\[rs]$0\[rs]f[]\"
1156 . Text .ds midpart was called with
1157 . Text .de print_args
1158 . Text .\ \ tm\ \*[@1]\ \[rs]*[midpart]\ \[rs]n[.$]\ \*[@2]
1159 . Text .\ \ tm\ \[rs]$*
1168 Unfortunately, draft mode cannot be used universally.
1170 Although it is good enough for defining normal macros, draft mode
1171 fails with advanced applications, such as indirectly defined
1172 strings, registers, etc.
1174 An optimal way is to define and test all macros in draft mode and then
1175 do the backslash doubling as a final step; do not forget to remove the
1180 .\" --------------------------------------------------------------------
1181 .SS "Tips for Macro Definitions"
1182 .\" --------------------------------------------------------------------
1185 Start every line with a dot, for example, by using the groff request
1187 for text lines, or write your own macro that handles also text lines
1194 . Text .\ \ if (\[rs]\[rs]n[.$] == 0)\ \[rs]
1195 . Text .\ \ \ \ return
1196 . Text .\ nop\ \[rs])\[rs]\[rs]$*[rs]\)
1202 Write a comment macro that works both for copy-in and draft mode; for
1203 as escaping is off in draft mode, trouble might occur when normal
1206 For example, the following macro just ignores its arguments, so it
1207 acts like a comment line:
1214 . Text .c\ This\ is\ like\ a\ comment\ line.
1219 In long macro definitions, make ample use of comment lines or empty
1220 lines for a better structuring.
1223 To increase readability, use groff's indentation facility for requests
1224 and macro calls (arbitrary whitespace after the leading dot).
1227 .\" --------------------------------------------------------------------
1229 .\" --------------------------------------------------------------------
1231 Diversions can be used to realize quite advanced programming
1234 They are comparable to pointers to large data structures in the
1235 C\~programming language, but their usage is quite different.
1239 In their simplest form, diversions are multi-line strings, but
1240 they get their power when diversions are used dynamically within macros.
1242 The information stored in a diversion can be retrieved by calling the
1243 diversion just like a macro.
1247 Most of the problems arising with diversions can be avoided if you are
1248 conscious about the fact that diversions always deal with complete
1251 If diversions are used when the line buffer has not been flashed,
1252 strange results are produced; not knowing this, many people get
1253 desperate about diversions.
1255 To ensure that a diversion works, line breaks should be added at the
1258 To be on the secure side, enclose everything that has to do with
1259 diversions into a pair of line breaks; for example, by amply using
1263 This rule should be applied to diversion definition, both inside and
1264 outside, and to all calls of diversions.
1266 This is a bit of overkill, but it works nicely.
1270 [If you really need diversions which should ignore the current partial
1271 line, use environments to save the current partial line and/\:or use the
1277 The most powerful feature using diversions is to start a diversion
1278 within a macro definition and end it within another macro.
1280 Then everything between each call of this macro pair is stored within
1281 the diversion and can be manipulated from within the macros.
1284 .\" --------------------------------------------------------------------
1286 .\" --------------------------------------------------------------------
1288 All macro names must be named
1290 to fully use the tmac mechanism.
1293 as with classical packages is possible as well, but deprecated.
1297 The macro files are kept in the
1298 .IR "tmac directories" ;
1299 a colon separated list of these constitutes the
1304 The search sequence for macro files is (in that order):
1307 the directories specified with troff/groff's
1312 the directories given in the
1313 .Env_var $GROFF_TMAC_PATH
1314 environment variable
1317 the current directory (only if in unsafe mode, which is enabled by the
1319 command line switch)
1325 a platform-specific directory, being
1327 in this installation
1330 a site-specific (platform-independent) directory, being
1332 in this installation
1335 the main tmac directory, being
1337 in this installation
1340 .\" --------------------------------------------------------------------
1342 .\" --------------------------------------------------------------------
1345 .Env_var $GROFF_TMAC_PATH
1346 A colon separated list of additional tmac directories in which to search
1349 See the previous section for a detailed description.
1352 .\" --------------------------------------------------------------------
1354 .\" --------------------------------------------------------------------
1356 Copyright (C) 2000, 2001, 2002, 2003, 2004, 2006
1357 Free Software Foundation, Inc.
1360 This document is distributed under the terms of the FDL (GNU Free
1361 Documentation License) version 1.1 or later.
1363 You should have received a copy of the FDL on your system, it is also
1364 available on-line at the
1365 .URL http://\:www.gnu.org/\:copyleft/\:fdl.html "GNU copyleft site" .
1368 This document is part of
1370 the GNU roff distribution.
1373 .MTO bwarken@mayn.de "Bernd Warken" ;
1375 .MTO wl@gnu.org "Werner Lemberg" .
1378 .\" --------------------------------------------------------------------
1380 .\" --------------------------------------------------------------------
1382 A complete reference for all parts of the groff system is found in the
1389 .BR groff (@MAN1EXT@)
1390 an overview of the groff system.
1394 .BR groff_man (@MAN7EXT@),
1396 .BR groff_mdoc (@MAN7EXT@),
1398 .BR groff_me (@MAN7EXT@),
1400 .BR groff_mm (@MAN7EXT@),
1402 .BR groff_mom (@MAN7EXT@),
1404 .BR groff_ms (@MAN7EXT@),
1406 .BR groff_trace (@MAN7EXT@),
1408 .BR groff_www (@MAN7EXT@).
1409 the groff tmac macro packages.
1413 .BR groff (@MAN7EXT@)
1418 The Filesystem Hierarchy Standard is available at the
1419 .URL http://\:www.pathname.com/\:fhs/ "FHS web site" .
1421 .cp \n[groff_tmac_C]
1423 .\" Local Variables: