ENV(1)

📦 version 0.12.0, in arch rolling

💅 ENV(1) — the env girlies' era ✨

okay so bestie, you know how this whole page is from the General Commands Manual? yeah. that's the manual it lives in. and the command is literally called env, lowercase, iconic. we're doing this together, you and me, right now 🫶

✨ NAME ✨

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

like, it sets variables AND runs your command. multitasking queen behavior, honestly 👑

🦋 SYNOPSIS 🦋

env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...]

that's it. that's the whole shape of it. options, maybe a -, then your NAME=VALUE pairs, then the command and its args. gorgeous, no notes 💖

🌸 DESCRIPTION 🌸

Set each NAME to VALUE in the environment and run COMMAND

yes that's literally the whole description and yes i'm repeating it because it's the entire personality of the command. you give it variables, it puts them in the environment, then it runs your COMMAND. periodt 🔥

🎀 OPTIONS 🎀

  • -i, --ignore-environment — start with an empty environment. like a clean slate, a fresh start, a factory reset for your vibes ✨
  • -C, --chdir <DIR> — change working directory to DIR. we're moving, bestie 🚚
  • -0, --null — end each output line with a 0 byte rather than a newline (only valid when printing the environment). ngl this is for when your filenames are chaotic and newlines just can't be trusted 💀 note the "only valid when printing the environment" part, ok? respect the constraint 🙈
  • -f, --file <PATH> — read and set variables from a ".env"-style configuration file (prior to any unset and/or set). order matters, she does the file thing first 🍓
  • -u, --unset <NAME> — remove variable from the environment. bye bestie, you're not invited 👋
  • -v, --debug — print verbose information for each processing step. she's narrating her whole process, main character energy fr 🔍
  • -S, --split-string <S> — process and split S into separate arguments; used to pass multiple arguments on shebang lines. this is the shebang-line girlie 🧚
  • -a, --argv0 <a> — override the zeroth argument passed to the command being executed. without this option a default value of command is used. so command is the fallback, got it 🎯
  • --ignore-signal[=<SIG>] — set handling of SIG signal(s) to do nothing. ignoring, but make it signal-handling 💅
  • --default-signal[=<SIG>] — reset handling of SIG signal(s) to the default action. back to factory settings, we love a reset 🌈
  • --block-signal[=<SIG>] — block delivery of SIG signal(s) while running COMMAND. not today, signal 🙅
  • --list-signal-handling — list signal handling changes requested by preceding options. receipts! she's showing you what the preceding options asked for 🧾
  • -h, --help — print help. we love a helper ⭐
  • -V, --version — print version. who are you? what's your number? 📞
  • [vars] — yep, that's listed right there in the options, so i'm listing it right here too. all the details, no skips, that's the rule 💜

💀 EXTRA 💀

A mere - implies -i. If no COMMAND, print the resulting environment.

so: lone dash = empty environment, and no command = she just prints the environment she built and dips. no cap, that's the whole extra section 😭

👑 VERSION 👑

v(uutils coreutils) 0.12.0

and that's the whole page, bestie. this icon of a manual page is dated 2026-09-17, it's version v(uutils coreutils) 0.12.0, and it's filed under ENV(1) in the General Commands Manual. go set some variables, i'm obsessed with you 🫶💖🌟

📦 where this page comes from