mtx-context(1)

✨ mtx-context ✨

okay bestie, so this is the manual page for mtx-context β€” aka ConTeXt Process Management πŸ’… it lives in the mtx-context(1) section of your man pages and it's literally the little engine that runs your ConTeXt documents. no cap.


🌸 NAME 🌸

mtx-context β€” ConTeXt Process Management πŸ’– that's the whole vibe.


πŸŽ€ SYNOPSIS πŸŽ€

mtxrun --script context [ OPTIONS ...  ] [ FILENAMES ]

like… you're calling it through mtxrun, using the context script, then you toss in whatever options you want and the files you want processed. simple as that 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

ConTeXt Process Management β€” yes that's the official line and yes it's iconic. it runs the whole show: formats, files, passes, purges, the works. main character energy fr fr πŸ‘‘


πŸ’– OPTIONS: BASIC πŸ’–

the everyday stuff. your bread and butter. your comfort options. πŸ“

  • --run β€” process (one or more) files (default action). this is the default bestie, so if you don't say anything else, this is what happens ✨
  • --make β€” create context formats πŸŽ€
  • *--ctx=name*</> β€” use ctx file (process management specification)
  • --noctx β€” ignore ctx directives and flags πŸ™ˆ
  • --interface β€” use specified user interface (default: en)
  • --autopdf β€” close pdf file in viewer and start pdf viewer afterwards. cute lil automatic preview moment πŸ¦‹
  • --purge β€” purge files either or not after a run (--pattern=...)
  • --purgeall β€” purge all files either or not after a run (--pattern=...)
  • *--usemodule=list* β€” load the given module or style, normally part of the distribution
  • *--environment=list* β€” load the given environment file first (document styles)
  • *--mode=list* β€” enable given the modes (conditional processing in styles)
  • *--path=list* β€” also consult the given paths when files are looked for
  • *--arguments=list* β€” set variables that can be consulted during a run (key/value pairs)
  • *--randomseed=number* β€” set the randomseed 🎲
  • *--result=name* β€” rename the resulting output to the given name
  • *--trackers=list* β€” set tracker variables (show list with --showtrackers)
  • *--directives=list* β€” set directive variables (show list with --showdirectives)
  • *--silent=list* β€” disable logcatgories (show list with --showlogcategories) β€” yes, "logcatgories", that's what it says, we don't make the rules πŸ’€
  • --strip β€” strip Lua code (only meant for production where no errors are expected)
⚠️ bestie, --strip is only meant for production where no errors are expected. don't be out here stripping in dev and then crying when you can't debug. πŸ’…
  • *--errors=list* β€” show errors at the end of a run, quit when in list (also when --silent)
  • --htmlerrorpage β€” generate html error page instead (optional: =scite)
  • --noconsole β€” disable logging to the console (logfile only)
  • --nodummy β€” don't create a dummy file (can confuse pdf viewers that keep file in view)
  • --purgeresult β€” purge result file before run
  • --forcexml β€” force xml stub
  • --forcecld β€” force cld (context lua document) stub
  • --forcelua β€” force lua stub (like texlua)
  • --forcemp β€” force mp stub
  • --arrange β€” run extra imposition pass, given that the style sets up imposition
  • --noarrange β€” ignore imposition specifications in the style
  • --pages β€” report pagenumbers of names pages and list references (--page=... or --page=...)
  • --jit β€” use luajittex with jit turned off (only use the faster virtual machine)
  • --jiton β€” use luajittex with jit turned on (in most cases not faster, even slower) 😭
  • --once β€” only run once (no multipass data file is produced)
  • --runs β€” process at most this many times
  • --forcedruns β€” process this many times (permits for optimization trial runs)
  • --batchmode β€” run without stopping and do not show messages on the console
  • --nonstopmode β€” run without stopping
  • --nosynctex β€” never initializes synctex (for production runs)
  • --synctex β€” run with synctex enabled (better use upsynctex[state=start])
  • --nodates β€” omit runtime dates in pdf file (optional value: a number (this 1970 offset time) or string "YYYY-MM-DD HH:MM")
  • --nocompression β€” forcefully turns off compression in the backend
  • --trailerid β€” alternative trailer id (or constant one)
  • --generate β€” generate file database etc. (as luatools does)
  • --paranoid β€” do not descend to .. and ../.. πŸ™ˆ
  • --version β€” report installed context version
  • --global β€” assume given file present elsewhere
  • --nofile β€” use dummy file as jobname

πŸ”₯ OPTIONS: EXPERT πŸ”₯

for when you're built different. the advanced girlies know. iykyk. πŸ’œ

  • --touch β€” update context version number (also provide --expert, optionally provide --basepath)
  • --nostatistics β€” omit runtime statistics at the end of the run
  • --profile β€” profile job (use: mtxrun --script profile --analyze)
  • --timing β€” generate timing and statistics overview
  • --keeptuc β€” keep previous tuc files (jobname-tuc-[run].tmp)
  • --keeppdf β€” keep previous pdf files (jobname-pdf-keep.tmp)
  • --keeplog β€” keep previous log files (jobname-log-[run].tmp)
  • --lmtx β€” force lmtx mode (when available)
  • --overloadmode=error|warning|0--6|255 β€” enable csname overload checking
  • *--extra=name* β€” process extra (mtx-context-... in distribution)
  • --extras β€” show extras
  • --ownerpassword β€” encrypt the (pdf) file using this master password πŸ”
  • --userpassword β€” use an additional password for opening the document
  • --permissions β€” list of: print, modify, extract, add, fillin, assemble, quality

πŸ’… OPTIONS: SPECIAL πŸ’…

the niche ones. the little side quests. obsessed honestly. 🌈

  • --pdftex β€” process file with texexec using pdftex
  • --xetex β€” process file with texexec using xetex
  • --mkii β€” process file with texexec
  • --pipe β€” do not check for file and enter scroll mode (--dummyfile=whatever.tmp)
  • --sandbox β€” process file in a limited environment
  • --addbinarypath β€” prepend the (found) binarypath to runners

πŸ‘‘ AUTHOR πŸ‘‘

More information about ConTeXt and the tools that come with it can be found at:

like, go say hi, the community is literally so sweet 🫢✨


and that's the whole page bestie!! this one's version 1.04, dated 01-01-2023 β€” mwah, go compile something gorgeous πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from