LIRC-LSPLUGINS(1)

💖 lirc-lsplugins — the manual, but make it make sense 💖

okay bestie, so this is lirc-lsplugins, a User Commands situation, and it's genuinely one of the most useful little gremlins in the whole lirc toolbox. sit down, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

lirc-lsplugins — print dynamic modules info. that's the whole vibe. it tells you what's in your plugin dirs and whether they're actually loadable. no cap.

---

🌈 SYNOPSIS 🌈

lirc-lsplugins [-l] [-q] [-U plugindir] [drivers]

lirc-lsplugins -e [-q] [-U plugindir]

lirc-lsplugins -y  [-U plugindir]

three whole moods, pick your fighter 💅

---

🦋 DESCRIPTION 🦋

so what does it do? it's the tool that writes out a simple lil list with info for every driver it finds. and like, the important part — it also tells you when a plugin can't be loaded, for example because of unresolved references. so it's not just flexing a list at you, it's doing a whole vibe check on your plugins. 🩺✨

the drivers argument is optional, and it's a selector — it narrows the output down to just the drivers that match. the match is a glob-type match, exactly like fnmatch() does it. so tira* energy. 🎀

---

💅 OPTIONS 💅

• -U, --plugindir <path> — use <path> to go searching for plugins. it's a ':'-separated search path, so basically the same energy as $PATH but for plugins. slay.
• -q, --quiet — don't write headers and don't write the trailing legend. just the raw goods. 🤫
• -s, --summary — just write a summary over the number of plugins, drivers and errors. the TL;DR option, obsessed.
• -e, --errors — only list plugins that can't be loaded, or that don't contain any drivers. the "who's failing bestie" mode. 😭
• -y, --yaml — make a YAML listing reflecting the drivers' configuration hints, like the device_hint. heads up tho: the format is unstable and it's primarily used by lirc-setup(1). so don't go building your whole life on it fr fr.
• -l, --long — add info on driver features. the extended director's cut. 🔥
• -p, --default-path — print the default search path and exit. that's it, that's the whole job. ✨
• -h, --help — display usage summary. your girl when you're lost.
• -v, --version — display version info. 👑

---

🎀 EXAMPLES 🎀

$ lirc-lsplugins -U ../lib/.libs:/usr/local/lib/lirc/plugins tira*

this lists all drivers with a name matching tira* found in plugins living in ../lib/.libs or /usr/local/lib/lirc/plugins. iconic. it's giving "show me every tira driver and nowhere else". 🌸

---

⭐ RETURN VALUE ⭐

lirc-lsplugins returns a non-zero error code if there's at least one plugin from which no driver can be loaded, or if options and parameters can't be parsed. otherwise? it returns zero. so zero = we're so back, non-zero = it's over. 💀

---

🙈 BUGS 🙈

lowkey a real one: some drivers change their capabilities at runtime, after inspecting the underlying hardware. those runtime capabilities can not be listed by lirc-lsplugins. so if something looks different at runtime than it does here, that's why — it's not you, it's the hardware inspection. 🫶

---

👑 SEE ALSO 👑

• fnmatch(3)
• lircd(8)

---

that's the whole page bestie, you ate it 💖 version lirc-lsplugins 0.10.2, last changed Oct 2016, and honestly? still serving. periodt. 🌈✨