<\/i>]<\/b><\/p>\nbegin using an initialized colour inline<\/p>\n
*[BCK<\/b> n<\/i>]<\/b><\/p>\n
move wards in a line<\/p>\n
*[BOLDER]
*[BOLDERX]<\/b><\/p>\n
Emboldening on\/off<\/p>\n
*[BOLDER]<\/b> begins emboldening type. *[BOLDERX]<\/b> turns the feature off. Both are inline escapes, therefore they should not appear as separate lines, but rather be embedded in text lines, like this:<\/p>\n
Not *[BOLDER]<\/b>everything*[BOLDERX]<\/b> is as it seems.<\/p>\n
Alternatively, if you wanted the whole line emboldened, you should do<\/p>\n
*[BOLDER]<\/b>Not everything is as it seems.*[BOLDERX]<\/b><\/p>\n
Once *[BOLDER]<\/b> is invoked, it remains in effect until turned off.<\/p>\n
Note: If you\u2019re using the document processing macros with .PRINTSTYLE TYPEWRITE<\/b>, mom<\/b> ignores *[BOLDER]<\/b> requests.<\/p>\n
*[BU<\/b> n<\/i>]<\/b><\/p>\n
move characters pairs closer together inline (related to macro .KERN<\/b>)<\/p>\n
*[COND]
*[CONDX]<\/b><\/p>\n
Pseudo-condensing on\/off<\/p>\n
*[COND]<\/b> begins pseudo-condensing type. *[CONDX]<\/b> turns the feature off. Both are inline escapes, therefore they should not appear as separate lines, but rather be embedded in text lines, like this:<\/p>\n
*[COND]<\/b>Not everything is as it seems.<\/i>*[CONDX]<\/b><\/p>\n
*[COND]<\/b> remains in effect until you turn it off with *[CONDX]<\/b>.<\/p>\n
IMPORTANT: You must turn *[COND]<\/b> off before making any changes to the point size of your type, either via the .PT_SIZE<\/b> macro or with the s<\/b> inline escape. If you wish the new point size to be pseudo-condensed, simply reinvoke *[COND]<\/b> afterwards. Equally, *[COND]<\/b> must be turned off before changing the condense percentage with .CONDENSE<\/b>.<\/p>\n
Note: If you\u2019re using the document processing macros with .PRINTSTYLE TYPEWRITE<\/b>, mom<\/b> ignores *[COND]<\/b> requests.<\/p>\n
*[CONDSUP]<\/b>…*[CONDSUPX]<\/b><\/p>\n
pseudo-condensed superscript<\/p>\n
*[DOWN<\/b> n<\/i>]<\/b><\/p>\n
temporarily move downwards in a line<\/p>\n
*[EN\u2212MARK]<\/b><\/p>\n
mark initial line of a range of line numbers (for use with line numbered endnotes)<\/p>\n
*[EXT]
*[EXTX]<\/b><\/p>\n
Pseudo-extending on\/off<\/p>\n
*[EXT]<\/b> begins pseudo-extending type. *[EXTX]<\/b> turns the feature off. Both are inline escapes, therefore they should not appear as separate lines, but rather be embedded in text lines, like this:<\/p>\n
*[EXT]<\/b>Not everything is as it seems.<\/i>*[EXTX]<\/b><\/p>\n
*[EXT]<\/b> remains in effect until you turn it off with *[EXTX]<\/b>.<\/p>\n
IMPORTANT: You must turn *[EXT]<\/b> off before making any changes to the point size of your type, either via the .PT_SIZE<\/b> macro or with the s<\/b> inline escape. If you wish the new point size to be pseudo-extended<\/i>, simply reinvoke *[EXT]<\/b> afterwards. Equally, *[EXT]<\/b> must be turned off before changing the extend percentage with .EXTEND<\/b>.<\/p>\n
Note: If you are using the document processing macros with .PRINTSTYLE TYPEWRITE<\/b>, mom<\/b> ignores *[EXT]<\/b> requests.<\/p>\n
*[EXTSUP]<\/b>…*[EXTSUPX]<\/b><\/p>\n
pseudo extended superscript<\/p>\n
*[FU<\/b> n<\/i>]<\/b><\/p>\n
move characters pairs further apart inline (related to macro .KERN<\/b>)<\/p>\n
*[FWD<\/b> n<\/i>]<\/b><\/p>\n
move forward in a line<\/p>\n
*[LEADER]<\/b><\/p>\n
insert leaders at the end of a line<\/p>\n
*[RULE]<\/b><\/p>\n
draw a full measure rule<\/p>\n
*[SIZE<\/b> n<\/i>]<\/b><\/p>\n
change the point size inline (related to macro .PT_SIZE<\/b>)<\/p>\n
*[SLANT]
*[SLANTX]<\/b><\/p>\n
Pseudo italic on\/off<\/p>\n
*[SLANT]<\/b> begins pseudo-italicizing type<\/i>. *[SLANTX]<\/b> turns the feature off. Both are inline escapes<\/i>, therefore they should not appear as separate lines, but rather be embedded in text lines, like this:<\/p>\n
Not *[SLANT]<\/b>everything*[SLANTX]<\/b> is as it seems.<\/p>\n
Alternatively, if you wanted the whole line pseudo-italicized<\/i>, you\u2019d do<\/p>\n
*[SLANT]<\/b>Not everything is as it seems.*[SLANTX]<\/b><\/p>\n
Once *[SLANT]<\/b> is invoked, it remains in effect until turned off.<\/p>\n
Note: If you\u2019re using the document processing macros with .PRINTSTYLE TYPEWRITE<\/b>, mom<\/b> underlines pseudo-italics by default. To change this behaviour, use the special macro .SLANT_MEANS_SLANT<\/b>.<\/p>\n
*[ST<\/b><\/i>]<\/b>…*[ST<\/b><\/i>X]<\/b><\/p>\nMark positions of string tabs<\/p>\n
The quad<\/i> direction must be LEFT<\/b> or JUSTIFY<\/b> (see .QUAD<\/b> and .JUSTIFY<\/b>) or the no-fill mode<\/i> set to LEFT<\/b> in order for these inlines to function properly. Please see IMPORTANT<\/i>, below.<\/p>\n
String tabs need to be marked off with inline escapes before being set up with the .ST<\/b> macro. Any input line may contain string tab markers. <\/i>, above, means the numeric identifier of the tab.<\/p>\nThe following shows a sample input line with string tab markers.<\/p>\n
*[ST1]<\/b>Now is the time*[ST1X]<\/b> for all *[ST2]<\/b>good men*ST2X]<\/b> to come to the aid of the party.<\/p>\n
String tab 1<\/i> begins at the start of the line and ends after the word time<\/i>. String tab 2<\/i> starts at good<\/i> and ends after men<\/i>. Inline escapes<\/i> (e.g. font<\/i> or point size changes<\/i>, or horizontal movements, including padding) are taken into account when mom<\/b> determines the position<\/i> and length<\/i> of string tabs<\/i>.<\/p>\n
Up to nineteen string tabs may be marked (not necessarily all on the same line, of course), and they must be numbered between 1 and 19.<\/p>\n
Once string tabs have been marked in input lines, they have to be set<\/i> with .ST<\/b>, after which they may be called, by number, with .TAB<\/b>.<\/p>\n
Note: Lines with string tabs marked off in them are normal input lines, i.e. they get printed, just like any input line. If you want to set up string tabs without the line printing, use the .SILENT<\/b> macro.<\/p>\n
IMPORTANT:<\/i> Owing to the way groff<\/b> processes input lines and turns them into output lines, it is not possible for mom<\/b> to guess<\/i> the correct starting position of string tabs marked off in lines that are centered or set flush right.<\/p>\n
Equally, she cannot guess the starting position if a line is fully justified and broken with .SPREAD<\/b>.<\/p>\n
In other words, in order to use string tabs, LEFT<\/b> must be active, or, if .QUAD LEFT<\/b> or JUSTIFY<\/b> are active, the line on which the string tabs<\/i> are marked must be broken manually<\/i> with .BR<\/b> (but not .SPREAD<\/b>).<\/p>\n
To circumvent this behaviour, I recommend using the PAD<\/b> to set up string tabs in centered or flush right lines. Say, for example, you want to use a string tab<\/i> to underscore<\/i> the text of a centered line with a rule. Rather than this,<\/p>\n
.CENTER
*[ST1]A line of text*[ST1X]c
.EL
.ST 1
.TAB 1
.PT_SIZE 24
.ALD 3p
*[RULE]
.RLD 3p
.TQ<\/b><\/p>\n
you should do:<\/p>\n
.QUAD CENTER
.PAD “#*[ST1]A line of text*[ST1X]#”
.EL
.ST 1
.TAB 1
.PT_SIZE 24
.ALD 3p
*[RULE] ” Note that you can\u2019t use *[UP] or *[DOWN] with *[RULE]
.RLD 3p
.TQ<\/b><\/p>\n
*[SUP]<\/b>…*[SUPX]<\/b><\/p>\n
superscript<\/p>\n
*[TB+]<\/b><\/p>\n
Inline escape for .TN<\/b> (Tab Next<\/i>)<\/p>\n
*[UL]<\/b>…*[ULX]<\/b><\/p>\n
invoke underlining inline (fixed width fonts only)<\/p>\n
*[UP<\/b> n<\/i>]<\/b><\/p>\n
temporarily move upwards in a line<\/p>\n
Details of Macros in alphabetical Order
.AUTOLEAD<\/b><\/p>\n
set the linespacing relative to the point size<\/p>\n
.B_MARGIN<\/b> <\/i><\/p>\nBottom Margin<\/p>\n
Requires a unit of measure<\/p>\n
.B_MARGIN<\/b> sets a nominal position at the bottom of the page beyond which you don\u2019t want your type to go. When the bottom margin is reached, mom<\/b> starts a new page. .B_MARGIN requires a unit of measure.<\/b> Decimal fractions are allowed. To set a nominal bottom margin of 3\/4 inch, enter<\/p>\n
.B_MARGIN .75i<\/b><\/p>\n
Obviously, if you haven\u2019t spaced the type on your pages so that the last lines fall perfectly at the bottom margin, the margin will vary from page to page. Usually, but not always, the last line of type that fits on a page before the bottom margin causes mom to start a new page.<\/p>\n
Occasionally, owing to a peculiarity in groff<\/i>, an extra line will fall below the nominal bottom margin. If you\u2019re using the document processing macros, this is unlikely to happen; the document processing macros are very hard-nosed about aligning bottom margins.<\/p>\n
Note: The meaning of .B_MARGIN<\/b> is slightly different when you\u2019re using the document processing macros.<\/p>\n
.FALLBACK_FONT<\/b> <\/i> [ ABORT | WARN ]<\/b><\/p>\nFallback Font<\/p>\n
In the event that you pass an invalid argument to .FAMILY<\/b> (i.e. a non-existent family<\/i>), mom<\/b>, by default, uses the fallback font<\/i>, Courier Medium Roman<\/b> (CR<\/b>), in order to continue processing your file.<\/p>\n
If you\u2019d prefer another fallback font<\/i>, pass .FALLBACK_FONT<\/b> the full family+font name<\/i> of the font<\/i> you\u2019d like. For example, if you\u2019d rather the fallback font<\/i> were Times Roman Medium Roman<\/b>,<\/p>\n
.FALLBACK_FONT TR<\/b><\/p>\n
would do the trick.<\/p>\n
Mom<\/b> issues a warning whenever a font style set<\/i> with .FT<\/b> does not exist, either because you haven\u2019t registered the style or because the font style<\/i> does not exist in the current family set<\/i> with .FAMILY<\/b>. By default, mom<\/b> then aborts, which allows you to correct the problem.<\/p>\n
If you\u2019d prefer that mom<\/b> not abort on non-existent fonts<\/i>, but rather continue processing using a fallback font<\/i>, you can pass .FALLBACK_FONT<\/b> the argument WARN<\/b>, either by itself, or in conjunction with your chosen fallback font<\/i>.<\/b><\/p>\n
Some examples of invoking .FALLBACK_FONT<\/b>:
.FALLBACK_FONT WARN<\/b><\/p>\n
mom<\/b> will issue a warning whenever you try to access a non-existent font<\/i> but will continue processing your file with the default fallback font<\/i>, Courier Medium Roman<\/b>.<\/p>\n
.FALLBACK_FONT TR WARN<\/b><\/p>\n
mom<\/b> will issue a warning whenever you try to access a non-existent font<\/i> but will continue processing your file with a fallback font<\/i> of Times Roman Medium Roman<\/b>; additionally, TR<\/b> will be the fallback font<\/i> whenever you try to access a family<\/i> that does not exist.<\/p>\n
.FALLBACK_FONT TR ABORT<\/b><\/p>\n
mom<\/b> will abort whenever you try to access a non-existent font<\/b>, and will use the fallback font<\/i> TR<\/b> whenever you try to access a family<\/i> that does not exist. If, for some reason, you want to revert to ABORT<\/b>, just enter “.FALLBACK_FONT ABORT”<\/b> and mom<\/b> will once again abort on font errors<\/i>.<\/p>\n
.FAM<\/b> <\/i><\/p>\nType Family, alias of .FAMILY<\/b><\/p>\n
.FAMILY<\/b> <\/i><\/p>\nType Family, alias .FAM<\/b><\/p>\n
.FAMILY<\/b> takes one argument: the name of the family<\/i> you want. Groff<\/i> comes with a small set of basic families, each identified by a 1-, 2- or 3-letter mnemonic. The standard families are:<\/p>\n
A = Avant Garde
BM = Bookman
H = Helvetica
HN = Helvetica Narrow
N = New Century Schoolbook
P = Palatino
T = Times Roman
ZCM = Zapf Chancery<\/b><\/p>\n
The argument you pass to .FAMILY<\/b> is the identifier at left, above. For example, if you want Helvetica<\/b>, enter<\/p>\n
.FAMILY H<\/b><\/p>\n
Note: The font macro (.FT<\/b>) lets you specify both the type family<\/i> and the desired font with a single macro. While this saves a few keystrokes, I recommend using .FAMILY for<\/b> family<\/i>, and .FT for<\/b> font<\/i>, except where doing so is genuinely inconvenient. ZCM<\/b>, for example, only exists in one style: Italic<\/b> (I<\/b>).<\/p>\n
Therefore,<\/p>\n
.FT ZCMI<\/b><\/p>\n
makes more sense than setting the family<\/i> to ZCM<\/b>, then setting the font<\/i> to I<\/i>.<\/p>\n
Additional note: If you are running a version of groff lower than 1.19.2, you must follow all .FAMILY<\/b> requests with a .FT<\/b> request, otherwise mom<\/b> will set all type up to the next .FT<\/b> request in the fallback font.<\/p>\n
If you are running a version of groff greater than or equal to 1.19.2, when you invoke the .FAMILY<\/b> macro, mom<\/b> remembers<\/i> the font style (<\/b>Roman, Italic<\/b>, etc) currently in use (if the font style exists in the new family<\/i>) and will continue to use the same font style in the new family. For example:<\/p>\n
.FAMILY BM<\/b> ” Bookman family<\/i>
.FT I<\/b> ” Medium Italic
” Bookman Medium Italic<\/i>
.FAMILY H<\/b> ” Helvetica family
” Helvetica Medium Italic<\/i><\/p>\nHowever, if the font style does not exist in the new family, mom<\/b> will set all subsequent type in the fallback font (by default, Courier Medium Roman<\/b>) until she encounters a .FT<\/b> request that\u2019s valid for the family<\/i>.<\/p>\n
For example, assuming you don\u2019t have the font Medium Condensed Roman<\/b> (mom<\/b> extension CD<\/i>) in the Helvetica family<\/i>:<\/p>\n
.FAMILY UN<\/b> ” Univers family<\/i>
.FT CD<\/b> ” Medium Condensed
” Univers Medium Condensed<\/i>
.FAMILY H<\/b> ” Helvetica family
” Courier Medium Roman!<\/i><\/p>\nIn the above example, you must follow .FAMILY H<\/b> with a .FT<\/b> request that\u2019s valid for Helvetica<\/b>.<\/p>\n
Please see the Appendices, Adding fonts to groff<\/i>, for information on adding fonts and families to groff, as well as to see a list of the extensions mom<\/b> provides to groff<\/i>\u2019s basic R<\/b>, I<\/b>, B<\/b>, BI<\/b> styles.<\/p>\n
Suggestion: When adding families to groff<\/i>, I recommend following the established standard for the naming families and fonts. For example, if you add the Garamond<\/b> family, name the font files<\/p>\n
GARAMONDR
GARAMONDI
GARAMONDB
GARAMONDBI<\/b><\/p>\n
GARAMOND then becomes a valid<\/b> family name<\/i> you can pass to .FAMILY<\/b>. (You could, of course, shorten GARAMOND<\/b> to just G<\/b>, or GD<\/b>.) R<\/b>, I<\/b>, B<\/b>, and BI<\/b> after GARAMOND<\/b> are the roman<\/i>, italic<\/i>, bold<\/i> and bold-italic<\/i> fonts respectively.<\/p>\n
.FONT R | B | BI |<\/b> <\/i><\/p>\nAlias to .FT<\/b><\/p>\n
.FT R | B | BI |<\/b> <\/i><\/p>\nSet font<\/p>\n
By default, groff<\/i> permits .FT<\/b> to take one of four possible arguments specifying the desired font:<\/p>\n
R = (Medium) Roman
I = (Medium) Italic
B = Bold (Roman)
BI = Bold Italic<\/b><\/p>\n
For example, if your family<\/i> is Helvetica<\/b>, entering<\/p>\n
.FT B<\/b><\/p>\n
will give you the Helvetica bold font<\/i>. If your family<\/i> were Palatino<\/b>, you\u2019d get the Palatino bold font<\/i>.<\/p>\n
Mom<\/b> considerably extends the range of arguments you can pass to .FT<\/b>, making it more convenient to add and access fonts of differing weights and shapes within the same family.<\/p>\n
Have a look here for a list of the weight\/style arguments mom<\/b> allows. Be aware, though, that you must have the fonts, correctly installed and named, in order to use the arguments. (See Adding fonts to groff<\/i> for instructions and information.) Please also read the ADDITIONAL NOTE<\/i> found in the description of the .FAMILY<\/b> macro.<\/p>\n
How mom<\/b> reacts to an invalid argument to .FT<\/b> depends on which version of groff you\u2019re using. If your groff version<\/i> is greater than or equal to 1.19.2, mom<\/b> will issue a warning and, depending on how you\u2019ve set up the fallback font, either continue processing using the fallback font, or abort (allowing you to correct the problem). If your groff version<\/i> is less than 1.19.2, mom<\/b> will silently continue processing, using either the fallback font or the font that was in effect prior to the invalid .FT<\/b> call.<\/p>\n
.FT<\/b> will also accept, as an argument, a full family<\/i> and font name<\/i>.<\/p>\n
For example,<\/p>\n
.FT HB<\/b><\/p>\n
will set subsequent type in Helvetica Bold<\/i>.<\/p>\n
However, I strongly recommend keeping family<\/i> and font<\/i> separate except where doing so is genuinely inconvenient.<\/p>\n
For inline control of fonts<\/i>, see Inline Escapes<\/i>, font control.<\/p>\n
.HI [<\/b> <\/i> ]<\/b><\/p>\nHanging indent \u2014 the optional argument requires a unit of measure.<\/p>\n
A hanging indent looks like this:<\/p>\n
The thousand injuries of Fortunato I had borne as best I
could, but when he ventured upon insult, I vowed
revenge. You who so well know the nature of my soul
will not suppose, however, that I gave utterance to a
threat, at length I would be avenged…<\/b><\/p>\n
The first line of text hangs<\/i> outside the left margin<\/i>.<\/p>\n
In order to use hanging indents<\/i>, you must first have a left indent<\/i> active (set with either .IL<\/b> or .IB<\/b>). Mom<\/b> will not hang text outside the left margin set<\/i> with .L_MARGIN<\/b> or outside the left margin<\/i> of a tab<\/i>.<\/p>\n
The first time you invoke .HI<\/b>, you must give it a measure<\/b>. If you want the first line of a paragraph to hang by<\/i>, say, 1 pica<\/i>, do<\/p>\n
.IL 1P
.HI 1P<\/b><\/p>\n
Subsequent invocations of .HI<\/b> do not require you to supply a measure<\/i>; mom<\/b> keeps track of the last measure you gave it.<\/p>\n
Generally speaking, you should invoke .HI<\/b> immediately prior to the line you want hung (i.e. without any intervening control lines). And because hanging indents<\/i> affect only one line, there\u2019s no need to turn them off.<\/p>\n
IMPORTANT:<\/i> Unlike IL<\/b>, IR<\/b> and IB<\/b>, measures given to .HI<\/b> are NOT additive. Each time you pass a measure to .HI ,<\/b> the measure is treated literally. Recipe:<\/i> A numbered list using hanging indents<\/i><\/p>\n
Note:<\/i> mom<\/b> has macros for setting lists. This recipe exists to demonstrate the use of hanging indents<\/i> only.<\/p>\n
.PAGE 8.5i 11i 1i 1i 1i 1i
.FAMILY T
.FT R
.PT_SIZE 12
.LS 14
.JUSTIFY
.KERN
.SS 0
.IL w\u2019\u0000\u0000.\u2019
.HI w\u2019\u0000\u0000.\u2019
1.\u0000The most important point to be considered is whether the
answer to the meaning of Life, the Universe, and Everything
really is 42. We have no-one\u2019s word on the subject except
Mr. Adams\u2019.
.HI<\/b>
2.\u0000If the answer to the meaning of Life, the Universe,
and Everything is indeed 42, what impact does this have on
the politics of representation? 42 is, after all not a
prime number. Are we to infer that prime numbers don\u2019t
deserve equal rights and equal access in the universe?
.HI<\/b>
3.\u0000If 42 is deemed non-exclusionary, how do we present it
as the answer and, at the same time, forestall debate on its
exclusionary implications?<\/p>\n
First, we invoke a left indent with a measure equal to the width of 2 figures spaces plus a period (using the w inline escape). At this point, the left indent is active; text afterwards would normally be indented. However, we invoke a hanging indent of exactly the same width, which hangs the first line (and first line only!) to the left of the indent by the same distance (in this case, that means \u201cout to the left margin\u201d). Because we begin the first line with a number, a period, and a figure space, the actual text (The most important point…<\/i>) starts at exactly the same spot as the indented lines that follow.<\/p>\n
Notice that subsequent invocations of .HI<\/b> don\u2019t require a measure<\/i> to be given.<\/p>\n
Paste the example above into a file and preview it with<\/p>\n
pdfmom filename.mom | ps2pdf \u2212 filename.pdf<\/b><\/p>\n
to see hanging indents in action.<\/p>\n
.IB [<\/b> <\/i> ]<\/b><\/p>\nIndent both \u2014 the optional argument requires a unit of measure<\/p>\n
.IB<\/b> allows you to set or invoke a left and a right indent at the same time.<\/p>\n
At its first invocation, you must supply a measure for both indents; at subsequent invocations when you wish to supply a measure, both must be given again. As with .IL<\/b> and .IR<\/b>, the measures are added to the values previously passed to the macro. Hence, if you wish to change just one of the values, you must give an argument of zero to the other.<\/p>\n
A word of advice:<\/i> If you need to manipulate left and right indents separately, use a combination of .IL<\/b> and .IR<\/b> instead of .IB<\/b>. You\u2019ll save yourself a lot of grief.<\/p>\n
A minus sign<\/i> may be prepended to the arguments to subtract from their current values. The w inline escape may be used to specify text-dependent measures, in which case no unit of measure is required. For example,<\/p>\n
.IB w’margarine’ w’jello’<\/b><\/p>\n
left indents text by the width of the word margarine<\/i> and right indents by the width of jello<\/i>.<\/p>\n
Like .IL<\/b> and .IR<\/b>, .IB<\/b> with no argument indents by its last active values. See the brief explanation of how mom handles indents for more details.<\/p>\n
Note:<\/i> Calling a tab<\/i> (with .TAB <\/b>) automatically cancels any active indents.<\/p>\nAdditional note:<\/i> Invoking .IB<\/b> automatically turns off .IL<\/b> and .IR<\/b>.<\/p>\n
.IL [<\/b> <\/i> ]<\/b><\/p>\nIndent left \u2014 the optional argument requires a unit of measure<\/p>\n
.IL<\/b> indents text from the left margin of the page, or if you\u2019re in a tab<\/i>, from the left edge of the tab<\/i>. Once IL<\/i> is on, the left indent<\/i> is applied uniformly to every subsequent line of text, even if you change the line length.<\/p>\n
The first time you invoke .IL<\/b>, you must give it a measure. Subsequent invocations with a measure add to the previous measure. A minus sign may be prepended to the argument to subtract from the current measure. The w<\/b> inline escape may be used to specify a text-dependent measure, in which case no unit of measure is required. For example,<\/p>\n
.IL w\u2019margarine\u2019<\/b><\/p>\n
indents text by the width of the word margarine<\/i>.<\/p>\n
With no argument, .IL<\/b> indents by its last active value. See the brief explanation of how mom<\/b> handles indents for more details.<\/p>\n
Note:<\/i> Calling a tab<\/i> (with .TAB <\/b>) automatically cancels any active indents.<\/p>\nAdditional note:<\/i> Invoking .IL<\/b> automatically turns off IB<\/b>.<\/p>\n
.IQ [<\/b> <\/i> ]<\/b><\/p>\nIQ \u2014 quit any\/all indents<\/p>\n
IMPORTANT NOTE:<\/i> The original macro for quitting all indents was .IX<\/b>. This usage has been deprecated in favour of IQ<\/b>. .IX<\/b> will continue to behave as before, but mom<\/b> will issue a warning to stderr<\/i> indicating that you should update your documents.<\/p>\n
As a consequence of this change, .ILX<\/b>, .IRX<\/b> and .IBX<\/b> may now also be invoked as .ILQ<\/b>, .IRQ<\/b> and .IBQ<\/b>. Both forms are acceptable.<\/p>\n
Without an argument, the macros to quit indents merely restore your original margins and line length. The measures stored in the indent macros themselves are saved so you can call them again without having to supply a measure.<\/p>\n
If you pass these macros the optional argument CLEAR<\/b>, they not only restore your original left margin and line length, but also clear any values associated with a particular indent style. The next time you need an indent of the same style, you have to supply a measure again.<\/p>\n
.IQ CLEAR<\/b>, as you\u2019d suspect, quits and clears the values for all indent styles at once.<\/p>\n
.IR [<\/b> <\/i> ]<\/b><\/p>\nIndent right \u2014 the optional argument requires a unit of measure<\/p>\n
.IR<\/b> indents text from the right margin<\/i> of the page, or if you\u2019re in a tab<\/i>, from the end of the tab<\/i>.<\/p>\n
The first time you invoke .IR<\/b>, you must give it a measure. Subsequent invocations with a measure add to the previous indent measure. A minus sign<\/i> may be prepended to the argument to subtract from the current indent measure. The w inline escape may be used to specify a text-dependent measure, in which case no unit of measure<\/i> is required. For example,<\/p>\n
.IR w\u2019jello\u2019<\/b><\/p>\n
indents text by the width of the word jello<\/i>.<\/p>\n
With no argument, .IR<\/b> indents by its last active value. See the brief explanation of how mom<\/b> handles indents for more details.<\/p>\n
Note:<\/i> Calling a tab<\/i> (with .TAB <\/b>) automatically cancels any active indents.<\/p>\nAdditional note:<\/i> Invoking .IR<\/b> automatically turns off IB<\/b>.<\/p>\n
.L_MARGIN<\/b> <\/i><\/p>\nLeft Margin<\/p>\n
L_MARGIN establishes the distance from the left edge of the printer sheet at which you want your type to start. It may be used any time, and remains in effect until you enter a new value.<\/p>\n
Left indents and tabs are calculated from the value you pass to .L_MARGIN<\/b>, hence it\u2019s always a good idea to invoke it before starting any serious typesetting. A unit of measure is required. Decimal fractions are allowed. Therefore, to set the left margin at 3 picas (1\/2 inch), you\u2019d enter either<\/p>\n
.L_MARGIN 3P<\/b><\/p>\n
or<\/p>\n
.L_MARGIN .5i<\/b><\/p>\n
If you use the macros .PAGE<\/b>, .PAGEWIDTH<\/b> or .PAPER<\/b> without invoking .L_MARGIN<\/b> (either before or afterwards), mom<\/b> automatically sets .L_MARGIN<\/b> to 1 inch<\/i>.<\/p>\n
Note: .L_MARGIN<\/b> behaves in a special way when you\u2019re using the document processing macros.<\/p>\n\n\n| <\/td>\n | \n .MCO<\/b><\/p>\n<\/td>\n | <\/td>\n | \n Begin multi-column setting.<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n .MCO<\/b> (Multi-Column On<\/i>) is the macro<\/i> you use to begin multi-column setting<\/i>. It marks the current baseline as the top of your columns, for use later with .MCR<\/b>. See the introduction to columns for an explanation of multi-columns<\/i> and some sample input.<\/p>\n Note:<\/i> Do not confuse .MCO<\/b> with the .COLUMNS<\/b> macro in the document processing macros.<\/p>\n\n\n| <\/td>\n | \n .MCR<\/b><\/p>\n<\/td>\n | <\/td>\n | \n Once you\u2019ve turned multi-columns<\/i> on (with .MCO<\/b>), .MCR<\/b>, at any time, returns you to the top of your columns<\/i>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n .MCX [<\/b> <\/i> ]<\/b><\/p>\nOptional argument requires a unit of measure.<\/p>\n .MCX<\/b> takes you out of any tab<\/i> you were in (by silently invoking .TQ<\/b>) and advances to the bottom of the longest column.<\/p>\n Without an argument, .MCX<\/b> advances 1 linespace<\/i> below the longest column.<\/p>\n Linespace, in this instance, is the leading in effect at the moment .MCX<\/b> is invoked.<\/p>\n If you pass the <\/i> argument to .MCX<\/b>, it advances 1 linespace<\/i> below the longest column (see above) PLUS<\/i> the distance specified by the argument. The argument requires a unit of measure; therefore, to advance an extra 6 points below where .MCX<\/b> would normally place you, you\u2019d enter<\/p>\n.MCX 6p<\/b><\/p>\n Note:<\/i> If you wish to advance a precise distance below the baseline of the longest column, use .MCX<\/b> with an argument of 0<\/b> (zero; no unit of measure<\/i> required) in conjunction with the .ALD<\/b> macro, like this:<\/p>\n .MCX 0
.ALD 24p<\/b><\/p>\n The above advances to precisely 24 points<\/i> below the baseline of the longest column.<\/p>\n .NEWPAGE<\/b><\/p>\n Whenever you want to start a new page, use .NEWPAGE<\/b>, by itself with no argument. Mom<\/b> will finish up processing the current page and move you to the top of a new one (subject to the top margin set with .T_MARGIN<\/b>).<\/p>\n .PAGE<\/b> <\/i> [<\/b> <\/i> [<\/b> <\/i> [<\/b> <\/i> [<\/b> <\/i> [<\/b> <\/i> ] ] ] ] ]<\/b><\/p>\nAll arguments require a unit of measure<\/p>\n IMPORTANT:<\/i> If you\u2019re using the document processing macros, | |