SHTK_CLI_DEBUG(3)

💅 SHTK_CLI_DEBUG 💅

okay bestie, welcome to the SHTK_CLI_DEBUG(3) page from the Library Functions Manual — it’s short, it’s cute, and it’s literally all about printing one debug message. let’s get into it 🫶

---

🌸 NAME 🌸

shtk_cli_debug — prints a debug message ✨

🎀 LIBRARY 🎀

shtk_import cli

🦋 SYNOPSIS 🦋

shtk_cli_debug message1 [.. messageN]

💖 DESCRIPTION 💖

so the shtk_cli_debug function prints the debug message you give it to stderr. yes, stderr, not stdout — she knows where she belongs 💅

you can pass the message as one or more arguments, shown here as message1 through messageN. all of those arguments get concatenated together into a single line. no cap, every argument becomes part of the same line ✨

the printed message has this exact form, where progname is determined by shtk_cli_progname(3):

progname: D: message1 .. messageN

debug-level messages are disabled by default and can be enabled with the shtk_cli_set_log_level(3) function. so yeah, shtk_cli_debug should be used to report information that is generally useful for debugging a problem and is not appropriate for regular usage. it’s giving “backstage pass only,” not main-character public output 🎀

lowkey important: debug messages are off by default, so don’t expect them to show up until debug-level logging is enabled with shtk_cli_set_log_level(3). periodt 💀

🌈 SEE ALSO 🌈

• shtk(3)
• shtk_cli(3)

⭐ HISTORY ⭐

shtk_cli_debug first appeared in shtk 1.7. iconic behavior, honestly 👑

---

this page came from Debian, dated February 3, 2016 — SHTK_CLI_DEBUG(3) signing off, mwah 💋💜