SHTK_CLI_SET_LOG_LEVEL(3)

✨ shtk_cli_set_log_level(3) — the "how loud should my logs be" manual page ✨

okay so this is a page from the shtk_cli_set_log_level manual, and honestly it's giving very useful, very main-character energy 💅 let me walk you through it bestie 🫶

🌸 NAME 🌸

shtk_cli_set_log_level — sets the level of the logging messages to display 💖

🎀 LIBRARY 🎀

shtk_import cli

🦋 SYNOPSIS 🦋

shtk_cli_set_log_level level

✨ DESCRIPTION ✨

so what does this function actually do? 💫 The shtk_cli_set_log_level function sets the maximum logging level of the messages that will be sent to stderr. That's literally it, and it's iconic for it.

The possible values for level are, in order of severity: error, warning, info and debug — and each one corresponds to the various functions of the form <level> in shtk_cli_<level> style 👑

For example: setting the level to warning would display error-level and warning-level messages but would omit info-level and debug-level messages. ngl that's literally the perfect way to implement a quiet/verbose mode in applications 🔥

💀 important to note: error-level messages are always displayed, because the minimum logging level that can be set is error. so like, you cannot silence the errors, bestie, they will find you 😭

The current log level can be programmatically queried with the shtk_cli_log_level(3) function ✨ and the default level corresponds to info 🎀

👑 SEE ALSO 👑

shtk(3), shtk_cli_log_level(3)

🌈 HISTORY 🌈

shtk_cli_set_log_level first appeared in shtk 1.7 ⭐

---

okay that's the whole vibe check ✅ this page is from the Debian crew, dated February 3, 2016, and it's part of the shtk manual — periodt 💖🫶