SHTK_CONFIG_UNSET(3)

💅 shtk_config_unset — the "ahem, actually" of config variables

okay bestie, welcome to SHTK_CONFIG_UNSET(3) from the Library Functions Manual ✨ this is the page where we learn how to make a config variable just… not exist anymore 🫶

🌈 LIBRARY

shtk_import config — that's the import you need, no cap 💖

🎀 SYNOPSIS

shtk_config_unset var_name

✨ DESCRIPTION

so the shtk_config_unset function unsets the value of the configuration variable var_name. like, poof, gone, main character exit 💅

and here's the slay part: it is OK to call shtk_config_unset even if var_name has never been previously set. no drama, no error, it just vibes. 🦋

BUT — and this is the important bit, iykyk — the given configuration variable must be a valid configuration variable as previously specified by a call to shtk_config_init(3). yes babes, that's the prerequisite. 🙈

💀 ERRORS

if var_name is invalid because it has not been registered as a valid configuration variable with a call to shtk_config_init(3), execution terminates with an error. not me finding out the hard way 😭 so pls register first, okay?

lowkey treat shtk_config_init(3) like the vibe check before the party — no registration, no entry. 🔥

👑 SEE ALSO

• shtk(3)
• shtk_config(3)

🌸 HISTORY

shtk_config_unset first appeared in shtk 1.0. iconic from day one, honestly ⭐

---

and that's the whole page, fr fr 💜 this Debian-era cutie is dated November 6, 2014, so go forth and unset responsibly — mwah 🎀