GLABELS-BATCH-QT(1)

πŸ“¦
version 3.99-master638 Β· 2 versions
, in nixpkgs unstable, ubuntu stonking

✨ glabels-batch-qt β€” the "print my labels from the terminal" era ✨

okay so bestie, imagine you made a whole cute label project in gLabels and now you want it printed without ever touching the GUI. that's literally what this is. glabels-batch-qt is a utility for printing a glabels project file from the command line. she takes exactly one project file, FILE, and that's it. no extra files, no "oops I passed three", just one.

and if FILE is -? then she's expecting an XML glabels project to be handed to her on standard input. yes, piping is valid and we love her for it. πŸ’–

glabels-batch-qt [options] FILE

πŸŽ€ OPTIONS πŸŽ€

every single flag, no skips, periodt:

  • -h, --help β€” shows you the usage info and then dips. bless. πŸ™ˆ
  • -v, --version β€” short lil version info, then exits.
  • -V, --Version β€” the detailed version info (yes the capital V matters, she's different), then exits.
  • -p <printer>, --printer <printer> β€” send the output to printer. your fave printer, chosen by you. πŸ–¨οΈ
  • -i <source>, --input <source> β€” set the merge input to source, which is typically a filename. if source is -, she reads from standard input. and heads up: this option overrides the merge source specified in the original glabels project file. she said "your project's default? cute. we're doing this instead." πŸ’…
  • -o [<filename>], --output [<filename>] β€” set the output filename to filename. if filename is -, she writes to standard output. (Default="output.pdf")
  • -s <n>, --sheets <n> β€” for simple projects, sets the number of full sheets to n. (Default=1)
  • -c <n>, --copies <n> β€” set the number of copies to n. (Default=1)
  • -a, --collate β€” collate merge copies. the whole set, together, in order. ✨
  • -g, --group β€” start each merge group on a new page. fresh page, fresh vibes. 🌸
  • -f <n>, --first <n> β€” set the starting position to n. (Default=1)
  • -l, --outlines β€” print label outlines. show me the borders, bestie. πŸ“
  • -m, --crop-marks β€” print crop marks. scissor girlies rise up. βœ‚οΈ
  • -r, --reverse β€” print in reverse (a mirror image). yes, everything flipped, intentionally.
  • -D <var>=<value>, --define <var>=<value> β€” set the initial value of user variable var to value. custom variables? slay. 🫢

πŸ¦‹ FILES πŸ¦‹

where everything lives, no cap:

  • ${prefix}/share/glabels-qt/templates/ β€” the directory holding all the predefined product templates that ship with glabels. the starter pack. πŸ‘‘
  • ${XDG_CONFIG_HOME}/glabels.org/glabels-qt/ β€” the directory for user defined product templates, the ones you made with the gLabels Product Template Designer.
⚠️ do NOT place manually created templates here!! she said what she said!! that folder is for Designer-made templates only, okay bestie? πŸ™ˆ
  • ${HOME}/.glabels/ β€” the directory for manually created product templates. this is where the handmade ones go. πŸ’–

πŸ’€ KNOWN ISSUES πŸ’€

okay this one's important so listen up.

On GNU/Linux platforms, glabels-batch-qt must be run from within a windowing environment, such as X or Wayland. why? because Qt requires a suitable platform to obtain system font information. she's dramatic like that. 😭

a work-around is to run glabels-batch-qt using a virtual X server environment:

xvfb-run glabels-batch-qt -o output.pdf myProject.glabels

xvfb-run save of the day, fr fr. 🌈


πŸ’œ REPORTING BUGS πŸ’œ

found a bug? want a feature? you can report both via the gLabels issue tracking system at GitHub (https://github.com/j-evins/glabels-qt/issues). fair warning: you will need a GitHub account to submit new issues or to comment on existing issues. that's just how it is. πŸŽ€


🌟 SEE ALSO 🌟


2020, Jaye Evins <evins@snaught.com>


and that's the whole page, bestie β€” this little icon of a manpage is from glabels-qt, dated Jan 01, 2026, and you literally just read the entire thing. obsessed with you for real. go print your labels. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from