MBK_TRACE_GETENV(1)

📦 version 5.1.1, in fedora 43, fedora 44

💖 MBK_TRACE_GETENV 💖

okay bestie, so this whole page lives in the MBK ENVIRONMENT VARIABLES corner of the manual (that's the mbk_trace_getenv(1) situation, section 1, iykyk) and it's about exactly one thing: making getenv() spill the tea. 🫖

🌈 NAME 🌈

MBK_TRACE_GETENV — defines getenv() debug output

Literally that's the whole job. She defines the debug output. Iconic of her, honestly. ✨

🏛️ ORIGIN 🏛️

This software belongs to the ALLIANCE CAD SYSTEM, developed by the ASIM team at the LIP6 laboratory of Université Pierre et Marie CURIE, in Paris, France. 🇫🇷 no cap, Paris.

🎀 SYNOPSIS 🎀

Bourne Shell:

MBK_TRACE_GETENV=yes; export MBK_TRACE_GETENV

C-shell:

sentenv MBK_TRACE_GETENV yes
not me just copying that second one exactly as written, because yes, it really does say sentenv up there and I am not about to gaslight you by "fixing" it. 🙈 Write what the page says, bestie.

💅 DESCRIPTION 💅

So here's the vibe check: if MBK_TRACE_GETENV is set to "yes", then all alliance tools will print debug info to stdout each and every time a getenv() syscall is done. Every. Single. Time. 👑

Not some of them. All of them. The whole alliance. It's giving group chat where everyone reads the receipts. 🔥

✨ OUTPUT EXAMPLE ✨

--- mbk --- mbkgetenv VH_PATSFX : pat

look at her. flawless. that's the shape of the little note you're gonna get spammed with. 🦋

🧚 SEE ALSO 🧚

go read those too, they're the lore. 💜

😭 BUG REPORT 😭

This tool is under development at the ASIM department of the LIP6 laboratory.

We need your feedback to improve documentation and tools.

fr fr please tell them stuff, they're asking so nicely 🥺

okay that's the whole page, you ate it, go set that variable and watch the debug output roll in like confetti 🌸🎀⭐

big love from the ASIM/LIP6 girlies, dated $Date: 2002/10/09 20:12:43 $, and yeah the file is MBK_TRACE_GETENV(1) — periodt. 💅💖

📦 where this page comes from