gecko-dev

История

Gregory Szorc 3d2bba6b22 Bug 1129798 - Use pdb.runcall to debug mach commands; r=ahal The previous debugger was setting a breakpoint in the mach dispatcher. This required users to step into the main function to be called into. Using pdb.runcall(), the debugger starts at the first line in the executed command, which is far more useful. --HG-- extra : rebase_source : 10734805ad40ec85eedbb089b11d618dc32398e7 extra : amend_source : da89da1af1f137db2f5902bcb5a69312f4636a4b		2015-02-04 22:49:06 -08:00
..
docs	Bug 1115278 - Fix mach documentation issues; r=glandium	2014-12-24 10:26:34 -08:00
mach	Bug 1129798 - Use pdb.runcall to debug mach commands; r=ahal	2015-02-04 22:49:06 -08:00
README.rst	Bug 1108399 - Move mach docs into sphinx; r=ahal	2014-12-07 10:40:19 -08:00
bash-completion.sh	Bug 950957 - Use ${COMP_WORDS[0]} for completion in mach. r=gps	2013-12-19 11:42:19 -05:00
setup.py	Bug 957856 - Synchronize mach with upstream repository; r=ahal	2014-01-08 16:14:39 -08:00

README.rst

====
mach
====

Mach (German for *do*) is a generic command dispatcher for the command
line.

To use mach, you install the mach core (a Python package), create an
executable *driver* script (named whatever you want), and write mach
commands. When the *driver* is executed, mach dispatches to the
requested command handler automatically.

To learn more, read the docs in ``docs/``.