env(1)

💖 env(1) — bestie's guide to setting env vars and running stuff 💖

okay so. you know how your shell has a whole little vibe board of environment variables? env is the girl who walks in, rearranges that board however you want, and then runs your command in the new ✨aesthetic✨. it's from uutils coreutils, and honestly? she ate.

---

🌸 NAME 🌸

env — set each NAME to VALUE in the environment and run COMMAND 🫶

---

🦋 SYNOPSIS 🦋

env [-i|--ignore-environment] [-C|--chdir] [-0|--null] [-f|--file]
[-u|--unset] [-v|--debug]... [-S|--split-string] [-a|--argv0]
[--ignore-signal] [--default-signal] [--block-signal]
[--list-signal-handling] [-h|--help] [-V|--version] [vars]

like, look at her. so many little flags, all valid, all iconic. 💅

---

👑 DESCRIPTION 👑

Set each NAME to VALUE in the environment and run COMMAND. that's it. that's the whole job. she sets the vibes, then she runs your command inside those vibes. no notes. 💖

---

✨ OPTIONS ✨

• -i, --ignore-environment — start with an empty environment. blank slate energy. no inherited variables, just vibes you brought yourself 🌈
• -C, --chdir <DIR> — change working directory to DIR before doing the thing 🚪
• -0, --null — end each output line with a 0 byte rather than a newline. heads up bestie: this is only valid when printing the environment — don't try it elsewhere, she will not be happy 💀
• -f, --file <PATH> — read and set variables from a ".env"-style configuration file (and yes, this happens prior to any unset and/or set, so order matters, ok? order always matters) 📄
• -u, --unset <NAME> — remove variable NAME from the environment. bye bestie, blocked, unfollowed 🚫
• -v, --debug — print verbose information for each processing step. she's telling you EVERYTHING she's doing, like a friend live-texting you through her whole day 📱
• -S, --split-string <S> — process and split S into separate arguments; used to pass multiple arguments on shebang lines. she's the one who can read the group chat and figure out who said what 🧚
• -a, --argv0 <a> — override the zeroth argument passed to the command being executed. without this option a default value of command is used. yes, she can change what the command thinks her own name is. main character rebranding 💅
• --ignore-signal[=<SIG>] — set handling of SIG signal(s) to do nothing. she saw the signal and simply chose to not perceive it 🙈
• --default-signal[=<SIG>] — reset handling of SIG signal(s) to the default action. back to factory settings, no baggage, fresh start 🌱
• --block-signal[=<SIG>] — block delivery of SIG signal(s) while running COMMAND. not today, signal. the door is closed 🔒
• --list-signal-handling — list signal handling changes requested by preceding options. receipts! she's showing you exactly what you asked for ✨
• -h, --help — print help
• -V, --version — print version
• [vars] — the actual NAME=VALUE pairs you wanna set, bestie. put them here. this is the moment 💖

---

🌈 EXTRA 🌈

A mere - implies -i. that's right, one lil dash and she's like "say less, empty environment it is."

If no COMMAND is given, she just prints the resulting environment instead. so you can peek at the vibes without committing to anything. window shopping but for env vars 🛍️

---

⭐ VERSION ⭐

v(uutils coreutils) 0.7.0

---

okay that's the whole page, you're basically an env girlie now 🎀 go set some variables, go run some commands, go be the main character of your own process environment. iykyk 💜

uu_env (uutils coreutils) 0.7.0 — env(1). mwah, love u, bye 🫶🌸