Markus Armbruster
4ea4a01fd5
(all): Depend on info. Flatten info directory. This undoes the move to one subdirectory per chapter, which was done during Empire 2. The structure doesn't buy us much, as the info name space is flat, and it complicates makefiles. Overhaul info.pl: - It now wants to run in the root of the build tree. - Information on source files and subjects is now stored in makefiles, thus info.pl no longer picks up random junk from the file system. - Clean up Perl anachronisms, in particular use subroutine arguments and results rather than global variables where convenient. - Change format of diagnostics to the common format used by GNU tools, so that Emacs and the like can parse it. - Catch missing .SA. - When creating a new subject file, cowardly refuse to overwrite an existing file. - Subject files contain topics sorted by chapter, then by name. The order of chapters used to depend on how Perl sorts hash keys. Fix it.
43 lines
1.4 KiB
Perl
43 lines
1.4 KiB
Perl
.TH Command WINGADD
|
|
.NA wingadd "Designate members of a \*Qwing\*U"
|
|
.LV Expert
|
|
.SY "wingadd <WING> <PLANE/WING>"
|
|
The wingadd command is used to specify the wing groupings
|
|
of your planes.
|
|
.s1
|
|
.EX wingadd <WING> <PLANE/WING>
|
|
In the syntax <WING> is the alphabetic character to be used as the
|
|
wing designation.
|
|
This character can be chosen from the set of
|
|
upper or lower case a-z and tilde (~).
|
|
The pseudo-wing specification tilde
|
|
specifies all planes not currently in any wing.
|
|
.s1
|
|
The specification of planes, <PLANE/WING>,
|
|
can have one of several syntaxes:
|
|
.NF
|
|
example meaning
|
|
------- -------
|
|
23 plane 23
|
|
2/14/23 planes 2, 14, and 23
|
|
c all planes currently in wing `c'
|
|
~ all planes currently in the \*Qnull\*U wing
|
|
2,3 all planes in sector 2,3
|
|
-1:3,0:2 all planes in the square area bounded by -1,0 & 3,2
|
|
.FI
|
|
All wings, (with the exception of the `~' wing),
|
|
are limited to some maximum size
|
|
and you will be informed how many planes can be added
|
|
when this command is run.
|
|
.s1
|
|
Having planes organized into wings can be very helpful in
|
|
loading, moving, etc.,
|
|
in that fewer commands are required to perform these commands
|
|
on groups of planes if they can be specified by wing number.
|
|
.s1
|
|
Note that you can remove planes from a wing by adding them to
|
|
the `~' wing. e.g.
|
|
.EX wingadd ~ A
|
|
This command would purge all planes from wing `A'.
|
|
.s1
|
|
.SA "plane, fly, Planes"
|