SHTK_CLI_LOG_LEVEL(3)

📦 version 1.7, in nixos 26.05, nixpkgs unstable

🌸 NAME 🌸

Okay so this is the SHTK_CLI_LOG_LEVEL(3) page, straight out of the Library Functions Manual, and it’s here for one very specific vibe check: is this logging level visible? ✨

  • shtk_cli_log_level — checks if the given logging level is visible 💅

🦋 LIBRARY 🦋

You get this by importing the cli library:

shtk_import cli

🎀 SYNOPSIS 🎀

shtk_cli_log_level level

✨ DESCRIPTION ✨

The shtk_cli_log_level function checks if the given logging level is currently being sent to stderr — like, is this level actually making it out to stderr right now, bestie? 👀

The possible values for level are, in order of severity:

  • error
  • warning
  • info
  • debug

And they correspond to the various functions of the form shtk_cli_<level> — iykyk 🫶

For example: after setting the level to warning, shtk_cli_log_level would return true for both error-level and warning-level messages, and would return false for both info-level and debug-level messages. No cap. 💖

⚠️ Important: error-level messages are always displayed. Always always. 💀

The current log level can be programmatically set with the shtk_cli_set_log_level(3) function, and the default level corresponds to info — that’s the starting vibe. 🌱

💖 SEE ALSO 💖

🌈 HISTORY 🌈

shtk_cli_log_level first appeared in shtk 1.7 — a certified icon since then 👑

Okay that’s the whole page! This Debian edition is dated February 3, 2016, and it’s the SHTK_CLI_LOG_LEVEL(3) manual page signing off. Slay your logs, bestie 💖✨

📦 where this page comes from