printenv

systemLinux/Unix

The printenv command is one of the most frequently used commands in Linux/Unix-like operating systems. printenv Print all or part of the environment

See Examples View Syntax

Quick Reference

Command Name:

printenv

Category:

system

Platform:

Linux/Unix

Basic Usage:

printenv [options] [arguments]

Common Use Cases

Syntax

printenv [OPTION]... [VARIABLE]...

Options

Option	Description
`-0, --null`	End each output line with a null byte rather than a newline
`--help`	Display help information and exit
`--version`	Output version information and exit

Examples

How to Use These Examples

The examples below show common ways to use the printenv command. Try them in your terminal to see the results. You can copy any example by clicking on the code block.

# Basic Examples Basic

printenv

Print all environment variables.

printenv HOME

Print the value of the HOME environment variable.

printenv USER PATH

Print the values of USER and PATH environment variables. # Advanced Examples Advanced printenv | grep PATH Show all environment variables containing PATH in their name. printenv | sort Print all environment variables, sorted alphabetically. if printenv DISPLAY >/dev/null; then echo "Display is set" else echo "Display is not set" fi Check if the DISPLAY variable is set. printenv | wc -l Count the number of environment variables. printenv -0 HOME | xxd Print HOME variable with a null separator and view in hex.

Try It Yourself

Practice makes perfect! The best way to learn is by trying these examples on your own system with real files.

Understanding Syntax

Pay attention to the syntax coloring: commands, options, and file paths are highlighted differently.

Notes

The `printenv` command is a Unix/Linux utility that displays the values of environment variables. Environment variables are dynamic named values that can affect the behavior of running processes on a computer. When used without any arguments, `printenv` displays all environment variables and their values. When used with one or more variable names as arguments, it prints only the values of those specific variables. Key features and uses of the `printenv` command include: 1. Environment Inspection: It allows users and scripts to examine the current environment settings. 2. Debugging: It's frequently used to debug issues related to environment variables, such as PATH problems or application configuration issues. 3. Script Validation: Scripts can use it to verify that required environment variables are set before proceeding with operations. 4. System Information: It provides access to system information like the username (USER), home directory (HOME), terminal type (TERM), and more. 5. Customization: Understanding the current environment helps users customize their shell experience. Common environment variables you might inspect with `printenv` include: - PATH: Lists directories that are searched for executable programs - HOME: The current user's home directory - USER or USERNAME: The current username - SHELL: The path to the current shell - LANG and LC_* variables: Language and locale settings - TERM: The terminal type - DISPLAY: The X display name for graphical applications - PWD: The current working directory The `printenv` command is similar to the `env` command, but with slightly different behavior. While `env` can also be used to modify the environment for a command execution, `printenv` is focused solely on displaying environment variables. In shell scripts, the command is often used in conditional statements to check for the existence or value of environment variables before performing certain operations. It's also commonly piped to other commands like `grep` to filter for specific variables, or `sort` to display variables in alphabetical order.

Related Commands

These commands are frequently used alongside printenv or serve similar purposes:

Use Cases

Learn By Doing

The best way to learn Linux commands is by practicing. Try out these examples in your terminal to build muscle memory and understand how the printenv command works in different scenarios.

See Examples Try Lab Exercises

$ printenv

View All Commands