I've been diving into how the `env` command operates and I have a question regarding its use. Specifically, I want to know if there's a functional difference between `var=value somecommand` and `env var=value somecommand`. Both methods seem to set the variable **var** for subshells and do not retain its value once `somecommand` finishes execution. Can anyone clarify when and why it's beneficial to use `env`? Thanks a lot!
1 Answer
The key difference lies in where the command is being executed. The `var=value somecommand` structure is a feature specific to shells and is only effective when the command line is processed by the shell itself. In contrast, `env` is a standalone program located in /bin, making it useful in situations where a proper shell isn't involved, such as when using `.desktop` files for launching applications. In those cases, `env` allows you to set environment variables without needing a shell.
Got it! So `env` helps in those scenarios where a full shell isn't available. It's interesting that as an actual command file, it doesn't need symbols like a pipe or semicolon after it—how does that work?