XMMS2-LAUNCHER(1)

πŸ’… XMMS2-LAUNCHER πŸ’…

okay so this is the xmms2-launcher page from the General Commands Manual β€” yes that's the manual section, we're fancy like that β€” and it's literally the lil matchmaker that gets xmms2d up and running for you. stay with me bestie, it's cute and it's short.


✨ NAME ✨

xmms2-launcher β€” the XMMS2 daemon launcher. that's it, that's the job. it launches the daemon. icon behavior honestly. πŸ‘‘


🌸 SYNOPSIS 🌸

xmms2-launcher [-l file] [-P file] [-v] [--] [XMMS2D_OPTION] ...
xmms2-launcher -h

like, two modes: launch it with vibes and options, or just ask for -h help. pick your main character moment. πŸ¦‹


πŸ’– DESCRIPTION πŸ’–

XMMS2 is a glow-up of the XMMS music player (yes, the one at https://en.wikipedia.org/wiki/XMMS). it's got a client-server model, which is the whole slay β€” it lets you run multiple user interfaces at the same time, and they can be textual or graphical, your choice, no gatekeeping. πŸ’… all the common audio formats are supported using plugins, and on top of that there's a flexible media library to organise your music. it's giving organized.

so what does xmms2-launcher actually do? it starts xmms2d(1) in the background. and here's the iconic part: it does not exit until the IPC system of XMMS2 is available. so the second the xmms2-launcher process has exited successfully, you know xmms2d(1) is ready to accept commands. no guessing, no "is it up yet", no refreshing like a maniac. it's a built-in vibe check. βœ…


πŸŽ€ OPTIONS πŸŽ€

heads up bestie: unrecognized options, and any options that show up beyond the pseudo-option --, get passed straight to xmms2d(1). so if something isn't listed here, it's not lost, it's just going to the daemon. 🫢

  • -l file, --logfile=file β€” write the log to file instead of the default log file location. keep your receipts somewhere specific. πŸ“
  • -P file, --pidfile=file β€” write the pid of xmms2d(1) to file. so you always know who's running the show. πŸ‘‘
  • -v, --verbose β€” make xmms2-launcher verbose. it will talk. a lot. we love a chatty icon. πŸ’¬
  • -?, -h, --help β€” show short help information and exit. yes, -? is real, it's quirky like that. πŸ™ˆ
  • -- β€” the pseudo-option marker; anything beyond this gets passed to xmms2d(1). it's the "everything after this line is not my business" line. 🚧
  • XMMS2D_OPTION β€” see xmms2d(1) for a list of options and their effect. go read that one, fr fr. πŸ“–

πŸ¦‹ FILES πŸ¦‹

okay so first, what even is CACHEDIR? let me break it down:

  • on UNIX, if the XDG_CACHE_HOME environment variable is set, CACHEDIR is $XDG_CACHE_HOME/xmms2.
  • otherwise it's $HOME/.cache/xmms2 β€” that's UNIX except Darwin.
  • on Darwin it's $HOME/Library/xmms2/logs.

cool? cool. now the file:

  • CACHEDIR/xmms2d.log β€” the default location for storing log output of xmms2d(1). that's where the lore lives. πŸ“š

🌈 ENVIRONMENT 🌈

  • XDG_CACHE_HOME β€” the location where the XMMS2 logs are located by default. set it, and CACHEDIR follows you there. ✨

πŸ”₯ SEE ALSO πŸ”₯

xmms2d(1), and https://github.com/xmms2. go click, go read, go be informed. πŸ’œ


⭐ HISTORY ⭐

the XMMS2 Project was started by Tobias RundstrΓΆm and Anders Waldenborg. it's developed by a small group of contributers from all over the world. small group, global reach, big slay. πŸŒπŸ’«


πŸ“ AUTHOR πŸ“

this manual page was written by Alexander Botero-Lowry <alex@foxybanana.com>. it was reformatted by Erik Massop <e.massop@hccnet.nl>. credit where credit is due, always. πŸŽ€


okay that's the whole page!! and a lil sign-off for the footer bestie: this was XMMS2-LAUNCHER(1) from the General Commands Manual β€” that's the source/version bit, and it's timeless, so no date needed. now go launch a daemon and be iconic πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from
  • arch rolling: xmms2 0.9.7-4 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms