fcft_log_init(3)

Hiii bestie! Welcome to the fcft manual β€” this is the page for fcft_log_init(3), and it's literally all about turning on and tuning fcft's logging. πŸŽ€

πŸŽ€ NAME πŸŽ€

fcft_log_init β€” configure logging in fcft πŸ’–

✨ SYNOPSIS ✨

#include <fcft/fcft.h>

void fcft_log_init(
    enum fcft_log_colorize colorize, bool do_syslog, enum fcft_log_class
    log_level);

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here's the tea: by default, fcft does not log anything. Not a peep. πŸ‘€ Use fcft_log_init() to enable logging and configure how it works in fcft. ✨

fcft_log_init() is typically called early, at program startup. 🫢

The colorize parameter is one of these, no cap:

enum fcft_log_colorize {
    FCFT_LOG_COLORIZE_NEVER,
    FCFT_LOG_COLORIZE_ALWAYS,
    FCFT_LOG_COLORIZE_AUTO
};

FCFT_LOG_COLORIZE_AUTO enables colors if stderr is a TTY. 🌈

If do_syslog is set, fcft will log to syslog, in addition to the regular logging on stderr. πŸ“¬

Note that fcft does not call openlog(), even if do_syslog is set. Do this from the calling application. Before, or after calling fcft_log_init() does not matter, as long as it is done before calling any other fcft API functions. ⚠️

Finally, log_level configures which types of log messages that will be shown. πŸ‘‘

enum fcft_log_class {
    FCFT_LOG_CLASS_NONE,
    FCFT_LOG_CLASS_ERROR,
    FCFT_LOG_CLASS_WARNING,
    FCFT_LOG_CLASS_INFO,
    FCFT_LOG_CLASS_DEBUG
};
Note that this is not a bitmask; setting FCFT_LOG_CLASS_INFO also enables FCFT_LOG_CLASS_WARNING and FCFT_LOG_CLASS_ERROR. 🫢

That's the whole page, bestie! πŸ’– This one's from the fcft manual, version 3.3.3, dated 2026-04-09, page fcft_log_init(3). Mwah πŸ’…βœ¨

πŸ“¦ where this page comes from