QTC(1)

πŸ“¦ version 1.8.0, in ubuntu stonking

✨ QTC(1) ✨

okay bestie, welcome to the qtc page πŸ’– that's the manual name btw, and yes it's the group chat you wanna be in.


🌸 NAME 🌸

qtc β€” template compiler (converter) for quicktemplate. yep, that's the whole vibe. it takes your pretty templates and turns them into Go code. iconic behavior fr fr πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

qtc [option...]

that's it. that's the whole summoning ritual. no positional args to stress about, just options πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so like. the qtc tool converts quicktemplate files into Go code. by default these files have a .qtpl extension, no cap.

it can be called directly, or via go generate β€” and lowkey the go generate route is the preferred form. the way that's the endorsed method?? yeah. do that one 🫢


πŸ’œ OPTIONS πŸ’œ

  • -dir string β€” path to the directory with template files to compile. only files with the -ext extension get compiled, see -ext for the deets.

the compiler recursively processes ALL the subdirectories. like, every single one, it's committed 😭 and the compiled template files get placed near the original file with .go extension added.

default value is "." ✨

  • -ext string β€” only files with this extension are compiled.

default is "qtpl".

  • -file string β€” path to the template file to compile. heads up: options -dir and -ext are ignored if file is set. like, they simply do not get a say πŸ™ˆ and the compiled template file will be placed near the original file with .go extension added.
  • -skipLineComments β€” do not write line comments.

⭐ lowkey reminder in case you skimmed (no judgement, I do it too): -dir and -ext get fully ignored the moment you set -file. so don't be out here setting all three and wondering why nothing makes sense πŸ’€

okay and for the sign-off πŸ’… this whole thing is from qtc version 1.8.0+ds1-4, dated 2026-05-19. periodt. go compile something cute bestie, you got this πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from