RUN_THEME_D_PROGRAM_M(1)
π RUN_THEME_D_PROGRAM_M(1) π
okay bestie, welcome to the run-theme-d-program-m manual page β it's section 1 of the manual, and it's literally all about running a modularly linked Theme-D program. yes. that's the whole job. she's a one-trick pony and she ATE. π
β¨ NAME β¨
run-theme-d-program-m β run a modularly linked Theme-D program π¦
β¨ SYNOPSIS β¨
run-theme-d-program-m [ METAARG ] ... PROGRAMFILE [ PROGRAMARG ] ...
β¨ DESCRIPTION β¨
so here's the tea π: the command run-theme-d-program-m runs a Theme-D program called PROGRAMFILE, linked modularly into Guile bytecode.
now β and this is the part people get confused about β the args split into two little teams:
METAARGargs get handled by therun-theme-d-program-mscript itself. she deals with those, not your program. πPROGRAMARGargs get passed straight through to your Theme-D program. those are hers to keep, bestie. π«Ά
β¨ OPTIONS β¨
-gPATHβ set the target library path. that's it, that's the whole vibe. πΈ--no-verbose-errorsβ no verbose info about errors (exceptions). keeping it lowkey. π€«--backtraceβ display a backtrace on runtime error. we love receipts. π₯--pretty-backtraceβ display a pretty printed backtrace on error. okay but heads up bestie, this one only works if you linked your Theme-D program with the option--runtime-pretty-backtrace. no link, no pretty. π--versionβ display backtrace on runtime error.
not me noticing that --version says it displays a backtrace on runtime error π that's what the page says, so that's what we're telling you. no edits, no notes, periodt. β
β¨ ENVIRONMENT β¨
THEME_D_CONFIG_FILEβ if this variable is defined, its value gets used as the Theme-D configuration file instead of the default configuration file. your file, your rules. πTHEME_D_CUSTOM_CODEβ a list of Guile bytecode files to be loaded before the Theme-D program runs. separate the filenames with colons. (:bestie, not commas, iykyk π§)
β¨ FILES β¨
/etc/theme-d-configβ the Theme-D configuration file. π~/.theme-d-configβ the Theme-D configuration file. this one should normally be present only if you use Theme-D in local mode. so if it's just... chilling there and you're not in local mode? side eye. π
β¨ SEE ALSO β¨
go read these too, they're all iconic in their own way π
run-theme-d-program(1)theme-d-compile(1)theme-d-link(1)setup-theme-d-test-env(1)/usr/share/doc/theme-d-doc/theme-d-user-guide.pdf.gz
reminder thatMETAARGs stay with the script andPROGRAMARGs go to your program. do not mix them up. i'm not mad, i'm just disappointed. π
GNU π 2025-08-18 β that's the source and the date, bestie, so go forth and run your modularly linked Theme-D program. slay, have fun, don't forget the colons in THEME_D_CUSTOM_CODE. mwah. πβ¨ππ¦πΈπ
π«Άπβ
π¦ where this page comes from
- ubuntu resolute: theme-d-rte 7.2.4-1 Β· GFDL-1.3-or-later
- ubuntu stonking: theme-d-rte 7.3.3-2 Β· GFDL-1.3-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms