Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!beta!unm-la!jay
From: jay@unm-la.UUCP (Jay Plett)
Newsgroups: comp.unix.questions,comp.text
Subject: Re: Troff - "Typesetter busy" message
Message-ID: <660@unm-la.UUCP>
Date: Wed, 29-Jul-87 23:22:40 EDT
Article-I.D.: unm-la.660
Posted: Wed Jul 29 23:22:40 1987
Date-Received: Sat, 1-Aug-87 02:17:04 EDT
References: <585@ritcv.UUCP> <643@ora.UUCP> <6196@brl-smoke.ARPA>
Organization: University of New Mexico - Los Alamos
Lines: 19
Summary: -m option
Xref: mnetor comp.unix.questions:3400 comp.text:1005

In article <6196@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
	[ stuff deleted ]
> Since -mx is actually an abbreviation for a filename, NOT an option
> (gross, isn't it?), it should follow all actual options.

-mx does indeed cause the file /usr/lib/tmac/tmac.x to be sourced.  But
it is an option.  Makes no difference whatsoever where you put it on
the command line.  The file isn't sourced until after all the options
are parsed.  The only time order of options is significant is when you
use multiple -m args (with newer releases of ditroff/nroff which allow
them), in which case the macro files are sourced in the order stated.
Still, they don't have to be consecutive and they may have other options
interspersed.  Like other options, -m options must precede any file-
name arguments.
-- 
	Jay Plett
	UUCP:	{cmcl2,ihnp4}!lanl!unm-la!jay
		{ucbvax,gatech}!unmvax!unm-la!jay
	ARPA:	jxyp@lanl.gov