This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Environment variable" – news ·newspapers ·books ·scholar ·JSTOR(May 2023) (Learn how and when to remove this message)

Anenvironment variable is a user-definablevalue that can affect the way runningprocesses will behave on a computer. Environment variables are part of the environment in which a process runs. For example, a running process can query the value of the TEMP environment variable to discover a suitable location to storetemporary files, or the HOME or USERPROFILE variable to find thedirectory structure owned by the user running the process.

They were introduced in their modern form in 1979 withVersion 7 Unix, so are included in allUnixoperating system flavors and variants from that point onward includingLinux andmacOS. FromPC DOS 2.0 in 1982, all succeedingMicrosoft operating systems, includingMicrosoft Windows, andOS/2 also have included them as a feature, although with somewhat different syntax, usage and standard variable names.

In allUnix andUnix-like systems, as well as on Windows, each process has its own separate set of environmentvariables. By default, when a process is created, it inherits a duplicaterun-time environment of its parent process, except for explicit changes made by the parent when it creates the child. At theAPI level, these changes must be done between runningfork andexec. Alternatively, fromcommand shells such asbash, a user can change environment variables for a particular command invocation by indirectly invoking it viaenv or using theENVIRONMENT_VARIABLE=VALUE <command> notation. A running program can access the values of environment variables for configuration purposes.

Shell scripts andbatch files use environment variables to communicate data and preferences tochild processes. They can also be used to store temporary values for reference later in a shell script. However, in Unix,non-exported variables are preferred for this as they do not leak outside the process.

In Unix, an environment variable that is changed in a script or compiled program will only affect that process and possibly child processes. The parent process and any unrelated processes will not be affected. Similarly, changing or removing a variable's value inside aDOS or Windows batch file will change the variable for the duration ofCOMMAND.COMorCMD.EXE's existence, respectively.

In Unix, the environment variables are normally initialized during system startup by the systeminitstartup scripts, and hence inherited by all other processes in the system. Users can, and often do, augment them in the profile script for the command shell they are using. In Microsoft Windows, each environment variable's default value is stored in theWindows Registry or set in theAUTOEXEC.BAT file.

OnUnix, asetuid program is given an environment chosen by its caller, but it runs with different authority from its caller. Thedynamic linker will usually load code from locations specified by the environment variables$LD_LIBRARY_PATH and$LD_PRELOAD and run it with the process's authority. If a setuid program did this, it would be insecure, because its caller could get it to run arbitrary code and hence misuse its authority. For this reason,libc unsets these environment variables at startup in a setuid process. setuid programs usually unset unknown environment variables and check others or set them to reasonable values.

In general, the collection of environment variables function as anassociative array where both the keys and values are strings. The interpretation of characters in either string differs among systems. When data structures such as lists need to be represented, it is common to use a colon (common on Unix and Unix-like) or semicolon-delineated (common on Windows and DOS) list.

The variables can be used both in scripts and on thecommand line. They are usually referenced by putting special symbols in front of or around the variable name.

It is conventional for environment-variable names to be chosen to be in all upper cases. In programming code generally, this helps to distinguish environment variables from other kinds of names in the code. Environment-variable names are case sensitive on Unix-like operating systems but not on DOS, OS/2, and Windows.

In most Unix and Unix-likecommand-line shells, an environment variable's value is retrieved by placing a$ sign before the variable's name. If necessary, the name can also be surrounded by braces.

To display the user home directory, the user may type:

echo$HOME

In Unix and Unix-like systems, the names of environment variables are case-sensitive.

The commandenv displays all environment variables and their values. The commandprintenv can also be used to print a single variable by giving that variable name as the sole argument to the command.

In DOS, OS/2 and Windows command-line interpreters such asCOMMAND.COM andCMD.EXE, an environment variable is retrieved by placing a% sign before and after it.

In DOS, OS/2 and Windows command-line interpreters as well as theirAPI, upper or lower case is not distinguished for environment variable names.

The environment variable namedHOMEDRIVE contains the drive letter (plus its trailing: colon) of the user's home directory, whilstHOMEPATH contains the full path of the user's home directory within that drive.

So to see the home drive and path, the user may type this:

ECHO%HOMEDRIVE%%HOMEPATH%

The commandSET (with no arguments) displays all environment variables and their values. InWindows NT and laterset can also be used to print all variables whose name begins with a given prefix by giving the prefix as the sole argument to the command.

InWindows PowerShell, the user may type any of the following:

echo$env:homedrive$env:homepathWrite-Output$env:homedrive$env:homepath"$env:homedrive$env:homepath"

In PowerShell, upper or lower case is not distinguished for environment variable names.

The following command displays all environment variables and their values:

get-childitemenv:

The commandsenv andset can be used to set environment variables and are often incorporated directly into the shell.

The following commands can also be used, but are often dependent on a certain shell.

VARIABLE=value         # (there must be no spaces around the equals sign)exportVARIABLE        # forBourne and related shells

exportVARIABLE=value  # forksh,bash, and related shells

setenvVARIABLEvalue  # forcsh and related shells

A few simple principles govern how environment variables achieve their effect.

Environment variables are local to the process in which they were set. If two shell processes are spawned and the value of an environment variable is changed in one, that change will not be seen by the other.

When a child process is created, it inherits all the environment variables and their values from the parent process. Usually, when a program calls another program, it first creates a child process byforking, then the child adjusts the environment as needed and lastly the childreplaces itself with the program to be called. This procedure gives the calling program control over the environment of the called program.

In Unix shells, variables may be assigned without theexport keyword. Variables defined in this way are displayed by theset command, but arenot true environment variables, as they are stored only by the shell and are unknown to all other processes. Theprintenv command will not display them, and child processes do not inherit them.

VARIABLE=value

The prefix syntax exports a "true" environment variable to a child process without affecting the current process:^[1]

VARIABLE=value program_name [arguments]

The persistence of an environment variable can be session-wide or system-wide.

unset is a builtin command implemented by both theBourne shell family (sh,ksh,bash, etc.) and theC shell family (csh, tcsh, etc.) ofUnix command line shells. It unsets a shell variable, removing it from memory and the shell's exported environment. It is implemented as ashell builtin, because it directly manipulates the internals of the shell.^[2][3] Read-only shell variables cannot be unset. If one tries to unset a read-only variable, theunset command will print an error message and return a non-zero exit code.

In DOS, OS/2 and Windows command-line interpreters such asCOMMAND.COM andCMD.EXE, theSET command is used to assign environment variables and values using the following arguments:

SETVARIABLE=value

An environment variable is removed via:

SETVARIABLE=

TheSET command without any arguments displays all environment variables along with their values;SET " ", zero or more spaces, will include internal variables too. InCMD.EXE, it is possible to assign local variables that will not be global using theSETLOCAL command andENDLOCAL to restore the environment.

Use theswitch/? to display the internaldocumentation, or use theviewerhelp:

SET/? HELP SETSETLOCAL /? HELP SETLOCAL

InPowerShell, the assignment follows a syntax similar to Unix:

$env:VARIABLE="VALUE"

Examples of environment variables include:

• PATH: a list of directory paths. When theuser types a command without providing the full path, this list is checked to see whether it contains a path that leads to the command.
• HOME (Unix-like) andUSERPROFILE (Microsoft Windows): indicate where a user'shome directory is located in thefile system.
• HOME/{.AppName} (Unix-like) andAPPDATA\{DeveloperName\AppName} (Microsoft Windows): for storing application settings. Many applications incorrectly useUSERPROFILE for application settings in Windows:USERPROFILE should only be used in dialogs that allow user to choose between paths likeDocuments/Pictures/Downloads/Music; for programmatic purposes,APPDATA (for roaming application settings shared across multiple devices),LOCALAPPDATA (for local application settings) orPROGRAMDATA (for application settings shared between multiple OS users) should be used.^[4]
• TERM (Unix-like): specifies the type ofcomputer terminal orterminal emulator being used (e.g.,vt100 ordumb).
• PS1 (Unix-like): specifies how the prompt is displayed in theBourne shell and variants.
• MAIL (Unix-like): used to indicate where a user's mail is to be found.
• TEMP: location where processes can store temporary files.

$PATH

Contains a colon-separated list of directories that the shell searches for commands that do not contain a slash in their name (commands with slashes are interpreted as file names to execute, and the shell attempts to execute the files directly). It is equivalent to theDOS,OS/2 andWindows%PATH% variable.

$HOME

Contains the location of the user'shome directory. Although the current user's home directory can also be found out through the C-functionsgetpwuid andgetuid,$HOME is often used for convenience in various shell scripts (and other contexts). Using the environment variable also gives the user the possibility to point to another directory.

$PWD

This variable points to the current directory. Equivalent to the output of the command pwd when called without arguments.

$DISPLAY

Contains the identifier for the display thatX11 programs should use by default.

$LD_LIBRARY_PATH

On many Unix systems with adynamic linker, contains a colon-separated list of directories that the dynamic linker should search forshared objects when building a process image afterexec, before searching in any other directories.

$LIBPATH or$SHLIB_PATH

Alternatives to$LD_LIBRARY_PATH typically used on older Unix versions.

$LANG, $LC_ALL, $LC_...

$LANG is used to set to the defaultlocale. For example, if the locale values arept_BR, then the language is set to (Brazilian) Portuguese and Brazilian practice is used where relevant. Different aspects of localization are controlled by individual$LC_-variables ($LC_CTYPE,$LC_COLLATE,$LC_DATE etc.).$LC_ALL can be used to force the same locale for all aspects.

$TZ

Refers totime zone. It can be in several formats, either specifying the time zone itself or referencing a file (in/usr/share/zoneinfo).

$BROWSER

Contains a colon-separated list of a user'sweb browser preferences, for use by programs that need to allow the user to view content at aURL. The browsers in the list are intended to be attempted from first to last, stopping after the first one that succeeds. This arrangement allows for fallback behavior in different environments, e.g., in anX11 environment, a graphical browser (such asFirefox) can be used, but in a console environment a terminal-base browser (such aLynx) can be used. A%s token may be present to specify where the URL should be placed; otherwise the browser should be launched with the URL as the first argument.^{[5][6][7][8][9]}

Under DOS, themaster environment is provided by the primary command processor, which inherits thepre-environment defined inCONFIG.SYS when first loaded. Its size can be configured through theCOMMAND /E:n parameter between 160^[10] and 32767^[10] bytes.Local environment segments inherited to child processes are typically reduced down to the size of the contents they hold. Some command-line processors (like4DOS) allow to define a minimum amount of free environment space that will be available when launching secondary shells.^[10] While the content of environment variables remains unchanged upon storage, their names (without the "%") are always converted to uppercase, with the exception ofpre-environment variables defined via theCONFIG.SYS directiveSET underDR DOS 6.0 and higher^[11][12] (and only withSWITCHES=/L (for "allow lowercase names") underDR-DOS 7.02 and higher).^[10][13] In principle,MS-DOS 7.0 and higher also supports lowercase variable names (%windir%), but provides no means for the user to define them. Environment variable names containing lowercase letters are stored in the environment just like normal environment variables, but remain invisible to most DOS software, since they are written to expect uppercase variables only.^[10][11][12] Some command processors limit the maximum length of a variable name to 80 characters.^[10] While principally only limited by the size of theenvironment segment, some DOS and 16-bit Windows programs^{[10][nb 1]} do not expect the contents of environment variables to exceed 128 characters. DR-DOSCOMMAND.COM supports environment variables up to 255,4DOS even up to 512 characters.^[10] SinceCOMMAND.COM can be configured (via/L:128..1024) to support command lines up to 1024 characters internally under MS-DOS 7.0 and higher, environment variables should be expected to contain at least 1024 characters as well. In some versions of DR-DOS, the environment passed to drivers, which often do not need their environment after installation, can be shrunken orrelocated throughSETENV orINSTALL[HIGH]/LOADHIGH options/Z (zero environment),/D[:loaddrive] (substitute drive, e.g.B:TSR.COM) and/E (relocate environment above program) in order to minimize the driver's effectively resulting residentmemory footprint.^{[14][13][11][15][16][17]}

In batch mode, non-existent environment variables are replaced by a zero-length string.

Standard environment variables orreserved environment variables include:

%APPEND% (supported since DOS 3.3)

This variable contains a semicolon-delimited list of directories in which to search for files. It is usually changed via theAPPEND /E command, which also ensures that the directory names are converted into uppercase. Some DOS software actually expects the names to be stored in uppercase and the length of the list not to exceed 121^[10] characters, therefore the variable is best not modified via theSET command.Long filenames containing spaces or other special characters must not be quoted (").

%CONFIG% (supported sinceMS-DOS 6.0 andPC DOS 6.1, also supported byROM-DOS^[18])

This variable holds the symbolic name of the currently chosen boot configuration. It is set by theDOS BIOS (IO.SYS,IBMBIO.COM, etc.) to the name defined by the correspondingCONFIG.SYS directiveMENUITEM before launching the primary command processor. Its main purpose is to allow further special cases inAUTOEXEC.BAT and similar batchjobs depending on the selected option at boot time. This can be emulated under DR-DOS by utilizing theCONFIG.SYS directiveSET likeSET CONFIG=1.

%CMDLINE% (introduced with4DOS, also supported sinceMS-DOS 7.0)

This variable contains the fully expanded text of the currently executing command line. It can be read by applications to detect the usage of and retrieve long command lines, since the traditional method to retrieve the command line arguments through thePSP (or relatedAPI functions) is limited to 126 characters and is no longer available whenFCBs get expanded or the defaultDTA is used. While 4DOS supports longer command lines,COMMAND.COM still only supports a maximum of 126 characters at the prompt by default (unless overridden with/U:128..255 to specify the size of the command line buffer), but nevertheless internal command lines can become longer through f.e. variable expansion (depending on/L:128..1024 to specify the size of the internal buffer). In addition to the command-line length byte in the PSP, the PSP command line is normally limited byASCII-13, and command lines longer than 126 characters will typically be truncated by having an ASCII-13 inserted at position 127,^[12] but this cannot be relied upon in all scenarios.^{[12][nb 2]} The variable will be suppressed for external commands invoked with a preceding@-symbol like in@XCOPY ... for backward compatibility and in order to minimize the size of the environment when loading non-relocatingterminate-and-stay-resident programs. Some beta versions ofWindows Chicago used%CMDLINE% to store only the remainder of the command line excessing 126 characters instead of the complete command line.^[11][12]

%COMSPEC% (supported since DOS 2.0)

This variable contains the full8.3 path to thecommand processor, typicallyC:\COMMAND.COM orC:\DOS\COMMAND.COM. It must not containlong filenames, but under DR-DOS it may containfile anddirectory passwords. It is set up by the primary command processor to point to itself (typically reflecting the settings of theCONFIG.SYS directiveSHELL), so that the resident portion of the command processor can reload its transient portion from disk after the execution of larger programs. The value can be changed at runtime to reflect changes in the configuration, which would require the command processor to reload itself from other locations. The variable is also used when launching secondary shells.

%COPYCMD% (supported sinceMS-DOS 6.2 andPC DOS 6.3, also supported byROM-DOS^[18])

Allows a user to specify the/Y switch (to assume "Yes" on queries) as the default for theCOPY,XCOPY, andMOVE commands. A default of/Y can be overridden by supplying the/-Y switch on the command line. The/Y switch instructs the command to replace existing files without prompting for confirmation.

%DIRCMD% (supported sinceMS-DOS 5.0 andPC DOS 5.0, also supported byROM-DOS^[18])

Allows a user to specify customized default parameters for theDIR command, including file specifications. Preset default switches can be overridden by providing the negative switch on the command line. For example, if%DIRCMD% contains the/W switch, then it can be overridden by usingDIR /-W at the command line. This is similar to the environment variable%$DIR% underDOS Plus^[19] and a facility to define default switches forDIR through its/C or/R switches underDR-DOSCOMMAND.COM.^[11]%DIRCMD% is also supported by the externalSDIR.COM/DIR.COMStacker commands underNovell DOS 7 and higher.^[11]

%LANG% (supported sinceMS-DOS 7.0)

This variable is supported by some tools to switch the locale for messages in multilingual issues.

%LANGSPEC% (supported sinceMS-DOS 7.0)

This variable is supported by some tools to switch the locale for messages in multilingual issues.

%NO_SEP% (supported sincePC DOS 6.3 andDR-DOS 7.07)

This variable controls the display ofthousands-separators in messages of various commands. Issued by default, they can be suppressed by specifyingSET NO_SEP=ON orSET NO_SEP=1 under PC DOS. DR-DOS additionally allows to override the system's thousands-separator displayed as in f.e.SET NO_SEP=..^[10]

%PATH% (supported since DOS 2.0)

This variable contains a semicolon-delimited list of directories in which thecommand interpreter will search forexecutable files. Equivalent to the Unix$PATH variable (but some DOS and Windows applications also use the list to search for data files similar to$LD_LIBRARY_PATH on Unix-like systems). It is usually changed via thePATH (orPATH /E underMS-DOS 6.0) command, which also ensures that the directory names are converted into uppercase. Some DOS software actually expects the names to be stored in uppercase and the length of the list not to exceed 123^[10] characters,^{[nb 1]} therefore the variable should better not be modified via theSET command.^[10]Long filenames containing spaces or other special characters must not be quoted ("). By default, the current directory is searched first, but some command-line processors like4DOS allow "." (for "current directory") to be included in the list as well in order to override this search order; some DOS programs are incompatible with this extension.^[10]

%PROMPT% (supported since DOS 2.0)

This variable contains a$-tokenized string defining the display of theprompt. It is usually changed via thePROMPT command.

%TEMP% (and%TMP%)

These variables contain the path to the directory wheretemporary files should be stored. Operating system tools typically only use%TEMP%, whereas third-party programs also use%TMP%. Typically%TEMP% takes precedence over%TMP%.

TheDR-DOS family supports a number of additionalstandard environment variables including:

%BETA%

This variable contains an optional message displayed by some versions (includingDR DOS 3.41) ofCOMMAND.COM at the startup of secondary shells.^[20]

%DRDOSCFG%/%NWDOSCFG%/%OPENDOSCFG%

This variable contains the directory^[21] (without trailing "\") where to search for.INI and.CFG configuration files (that is, DR-DOS application specific files likeTASKMGR.INI,TASKMAX.INI,VIEWMAX.INI,FASTBACK.CFG etc., class specific files likeCOLORS.INI, or global files likeDRDOS.INI,NWDOS.INI,OPENDOS.INI, orDOS.INI), as used by theINSTALL andSETUP commands and various DR-DOS programs likeDISKOPT,DOSBOOK,EDIT,FBX,FILELINK,LOCK,SECURITY.OVL/NWLOGIN.EXE,SERNO,TASKMAX,TASKMGR,VIEWMAX, orUNDELETE.^[11] It must not containlong filenames.

%DRCOMSPEC%

This variable optionally holds an alternative path to the command processor taking precedence over the path defined in the%COMSPEC% variable, optionally includingfile anddirectory passwords. Alternatively, it can hold a special value of "ON" or "1" in order to enforce the usage of the%COMSPEC% variable even in scenarios where the%COMSPEC% variable may point to the wrong command-line processor, for example, when running some versions of the DR-DOSSYS command under a foreign operating system.^[22]

%DRSYS%

Setting this variable to "ON" or "1" will force some versions of the DR-DOSSYS command to work under foreign operating systems instead of displaying a warning.^[22]

%FBP_USER%

Specifies the user name used by theFastBack commandFBX and{user}.FB configuration files underNovell DOS 7.^[11]

%HOMEDIR%

This variable may contain the home directory under DR-DOS (includingDR DOS 5.0 and6.0).^[11][20]

%INFO%

In some versions of DR-DOSCOMMAND.COM this variable defines the string displayed by the$I token of thePROMPT command.^[20] It can be used, for example, to inform the user how to exit secondary shells.

%LOGINNAME%

In some versions of DR-DOSCOMMAND.COM this variable defines the user name displayed by the$U token of thePROMPT command, as set up by f.e. login scripts forNovell NetWare.^[10][11][20] See also the similarly named pseudo-variable%LOGIN_NAME%.

%MDOS_EXEC%

This variable can take the values "ON" or "OFF" underMultiuser DOS. If enabled, the operating system permits applications to shell out to secondary shells with theDOS Program Area (DPA) freed in order to have maximum DOS memory available for secondary applications instead of running them in the same domain as under DOS.^[23][24]

%NOCHAR%

This variable can be used to define the character displayed by some commands in messages for "No" in[Y,N] queries, thereby overriding the current system default (typically "N" in English versions of DR-DOS). If it contains a string, only the first character, uppercased, will be taken. Some commands also support a command line parameter/Y to automatically assume "Yes" on queries, thereby suppressing such prompts. If, however, the parameter/Y:yn is used to specify the "Yes"/"No" characters (thereby overriding any%NOCHAR% setting), queries are not suppressed. See also the relatedCONFIG.SYS directiveNOCHAR and the environment variable%YESCHAR%.^[22]

%NOSOUND%

Setting this variable to "ON" or "1" will disable default beeps issued by some DR-DOS commands in certain situations such as to inform the user of the completion of some operation, that user interaction is required, or when a wrong key was pressed. Command line options to specifically enable certain beeps will override this setting.

%OS%

This variable contains the name of the operating system in order to distinguish between different DOS-related operating systems ofDigital Research-origin in batch jobs and applications.^[21] Known values include "DOSPLUS" (DOS Plus 1.2 in DOS emulation), "CPCDOS 4.1" (DOS Plus 1.2 inCP/M emulation), "DRDOS" (DR DOS 3.31-6.0,DR DOS Panther,DR DOS StarTrek,DR-DOS 7.02^[21]-7.05), "EZDOS" (EZ-DOS 3.41), "PALMDOS" and "NetWare PalmDOS" (PalmDOS 1.0), "NWDOS" (Novell DOS 7), "NWDOS7" (Novell DOS 7 Beta), "OPENDOS" (Caldera OpenDOS 7.01,Caldera DR-OpenDOS 7.02), "CDOS" (Concurrent DOS,Concurrent DOS XM), "CPCDOS" (Concurrent PC DOS), "CDOS386" (Concurrent DOS 386), "DRMDOS" (DR Multiuser DOS), "MDOS" (CCI Multiuser DOS),^[23] "IMSMDOS" (IMS Multiuser DOS), "REAL32" (REAL/32).^[11][25] MS-DOSINTERSVR looks for a value of "DRDOS" as well.^[25] See also the identically named environment variable%OS% later introduced in theWindows NT family.

%PEXEC%

In some versions of DR-DOS this variable defines the command executed by the$X token of thePROMPT command beforeCOMMAND.COM displays the prompt after returning from external program execution.^[11][21]

%SWITCHAR%

This variable defines theSwitChar to be used for argument parsing by some DR-DOS commands. If defined, it overrides the system's current SwitChar setting. The only accepted characters are "/" (DOS style), "-" (Unix style) and "[" (CP/M style). See also the relatedCONFIG.SYS directiveSWITCHAR (to set the system's SwitChar setting) and the%/%system information variable in some issues of DR-DOSCOMMAND.COM (to retrieve the current setting for portable batchjobs).

%TASKMGRWINDIR%

This variable specifies the directory, where theWindowsSYSTEM.INI to be used by the DR-DOSTASKMGR multitasker is located, overriding the default procedure to locate the file.^[11]

%VER%

This variable contains the version of the operating system in order to distinguish between different versions of DR-DOS in batch jobs and in the display of theVER command.^[21] It is also used for the$V token of thePROMPT command and affects the value returned by thesystem information variable%OS_VERSION%. Known values include "1.0" (PalmDOS 1.0), "1.2" (DOS Plus 1.2 in DOS emulation), "2.0" (Concurrent DOS 386 2.0), "3.0" (Concurrent DOS 386 3.0), "3.31" (DR DOS 3.31), "3.32" (DR DOS 3.32), "3.33" (DR DOS 3.33), "3.34" (DR DOS 3.34), "3.35" (DR DOS 3.35), "3.40" (DR DOS 3.40), "3.41" (DR DOS 3.41,EZ-DOS 3.41), "3.41T" (DR DOS 3.41T), "4.1" (Concurrent PC DOS 4.1), "5.0" (DR DOS 5.0,DR Multiuser DOS 5.0), "5.1" (Novell DR Multiuser DOS 5.1), "6.0" (DR Concurrent DOS XM 6.0,DR DOS 6.0), "6.2" (DR Concurrent DOS XM 6.2), "7" (Novell DOS 7,Caldera OpenDOS 7.01,DR-DOS 7.02-7.05), "7.00" (CCI Multiuser DOS 7.00), "7.07" (DR-DOS 7.07), "7.1" (IMS Multiuser DOS 7.1), "7.21" (CCI Multiuser DOS 7.21),^[23] "7.22" (CCI Multiuser DOS 7.22) etc.^[11][25][23]

%YESCHAR%

This variable can be used to define the character displayed by some commands in messages for "Yes" in[Y,N] queries, thereby overriding the current system default (typically "Y" in English versions of DR-DOS). If it contains a string, only the first character, uppercased, will be taken. Some commands also support a command line parameter/Y to automatically assume "Yes" on queries, thereby suppressing such prompts. If, however, the parameter/Y:y is used to specify the "Yes" character (thereby overriding any%YESCHAR% setting), queries are not suppressed. See also the relatedCONFIG.SYS directiveYESCHAR and the environment variable%NOCHAR%.^[22]

%$CLS%

This variable defines the control sequence to be sent to the console driver to clear the screen when theCLS command is issued, thereby overriding the internal default ("←[2J" under DR-DOS, "←E" underDOS Plus 1.2 on Amstrad machines^[19] as well as underConcurrent DOS,Multiuser DOS, andREAL/32 forVT52 terminals, or "←+" under Multiuser DOS forASCII terminals).^[23] If the variable is not defined and noANSI.SYS console driver is detected, the DR-DOSCOMMAND.COM will directly clear the screen viaINT 10h/AH=00hBIOS function, like MS-DOS/PC DOSCOMMAND.COM does. A special\nnn-notation foroctal numbers is supported to allow the definition of special characters like ESC (ASCII-27 = "←" = 1Bh = 33o), as f.e. inSET $CLS=\033[2J. To send the backslash ("\") itself, it can be doubled "\\".^[11][20][23]

%$DIR%

Supported byDOS Plus accepting the values "L" (long) or "W" (wide) to change the default layout of directory listings withDIR. Can be overridden using the command line options/L or/W.^[20][19] See also the similar environment variable%DIRCMD% and theDIR options/C and/R of the DR-DOS COMMAND.COM.^[11]

%$PAGE%

Supported byDOS Plus accepting the values "ON" or "OFF" for pagination control. Setting this to "ON" has the same affect as adding/P to commands supporting it (likeDIR orTYPE).^[20][19]

%$LENGTH%

Used byDOS Plus to define the screen length of the console in lines. This is used to control in a portable way when the screen output should be temporarily halted until a key is pressed in conjunction with the/P option supported by various commands or with automatic pagnination.^[20][19] See also the related environment variables%$WIDTH% and%DIRSIZE% as well as the similar pseudo-variable%_ROWS%.

%$WIDTH%

Used byDOS Plus to define the screen width of the console in columns. This is used to control in a portable way the formatting of the screen output of commands likeDIR /W orTYPE filename.^[20][19] See also the related environment variables%$LENGTH% and%DIRSIZE% as well as the similar pseudo-variable%_COLUMNS%.

%$SLICE%

Used byDOS Plus accepting a numerical value to control the foreground/background time slicing of multitasking programs.^[20][19] See also the DOS Plus commandSLICE.

%$ON%

This variable can hold an optional control sequence to switch text highlighting, reversion or colorization on. It is used to emphasize or otherwise control the display of the file names in commands likeTYPE wildcard, for exampleSET $ON=\033[1m withANSI.SYS loaded orSET $ON=\016 for an IBM orESC/P printer. For the special\nnn octal notation supported, see%$CLS%.^[11][19] While the variable is undefined by default under DOS Plus and DR-DOS, theMultiuser DOS default for anASCII terminal equalsSET $ON=\033p.^[20][23] See also the related environment variable%$OFF%.

%$OFF%

This variable can hold an optional control sequence to switch text highlighting, reversion or colorization off. It is used to return to the normal output after the display of file names in commands likeTYPE wildcard, for exampleSET $OFF=\033[0m withANSI.SYS loaded orSET $OFF=\024 for an IBM orESC/P printer. For the special\nnn octal notation supported, see%$CLS%.^[11][19] While the variable is undefined by default under DOS Plus and DR-DOS, theMultiuser DOS default for anASCII terminal equalsSET $OFF=\033q.^[20][23] See also the related environment variable%$ON%.

%$HEADER%

This variable can hold an optional control sequence issued before the output of the file contents in commands likeTYPE under DR-DOS 7.02 and higher. It can be used for highlighting, pagination or formatting, f.e. when sending the output to a printer, i.e.SET $HEADER=\017 for an IBM orESC/P printer. For the special\nnn octal notation supported, see%$CLS%.^[20] See also the related environment variable%$FOOTER%.

%$FOOTER%

This variable can hold an optional control sequence issued after the output of the file contents in commands likeTYPE under DR-DOS 7.02 and higher. It is used to return to the normal output format, i.e.SET $FOOTER=\022\014 in the printer example above. For the special\nnn octal notation supported, see%$CLS%.^[20] See also the related environment variable%$HEADER%.

Datalight ROM-DOS supports a number of additionalstandard environment variables as well including:

%DIRSIZE%

This variable is used to define non-standard screen sizesrows[,cols] forDIR options/P and/W (similar to%$LENGTH% and%$WIDTH% under DOS Plus).^[18]

%NEWFILE%

This variable is automatically set to the first parameter given to the CONFIG.SYS directiveNEWFILE.^[18]

%TZ%,%COMM%,%SOCKETS%,%HTTP_DIR%,%HOSTNAME% and%FTPDIR% are also used by ROM-DOS.^[18]

%BEGINLIBPATH%

Contains a semicolon-separated list of directories which are searched forDLLsbefore the directories given by the%LIBPATH% variable (which is set during system startup with the specialCONFIG.SYS directiveLIBPATH). It is possible to specify relative directories here, including "." for the current working directory. See also the related environment variable%ENDLIBPATH%.

%ENDLIBPATH%

a list of directories to be searched forDLLs like%BEGINLIBPATH%, but searchedafter the list of directories in%LIBPATH%.

These environment variables refer to locations of critical operating system resources, and as such generally are not user-dependent.^[26]

%APPDATA%

Contains the full path to theApplication Data directory of the logged-in user. Does not work on Windows NT 4.0 SP6 UK.

%LOCALAPPDATA%

This variable is the temporary files ofApplications. Its uses include storing ofdesktop themes,Windows error reporting, caching and profiles of web browsers.

%ComSpec%/%COMSPEC%

The%ComSpec% variable contains the full path to the command processor; on the Windows NT family of operating systems, this iscmd.exe, while onWindows 9x,%COMSPEC% isCOMMAND.COM.

%OS%

The%OS% variable contains a symbolic name of the operating system family to distinguish between differing feature sets inbatchjobs. It resembles an identically named environment variable%OS% found in all DOS-related operating systems ofDigital Research-origin like Concurrent DOS,Multiuser DOS, REAL/32,DOS Plus,DR DOS, Novell DOS and OpenDOS.%OS% always holds the string "Windows_NT" on theWindows NT family.^[27]

%PATH%

This variable contains a semicolon-delimited (do not put spaces in between) list of directories in which the command interpreter will search for an executable file that matches the given command. Environment variables that represent paths may be nested within the%PATH% variable, but only at one level of indirection. If this sub-path environment variable itself contains an environment variable representing a path,%PATH% will not expand properly in the variable substitution. Equivalent to theUnix$PATH variable.

%PROCESSOR_ARCHITECTURE%,%PROCESSOR_ARCHITEW6432%,%PROCESSOR_IDENTIFIER%,%PROCESSOR_LEVEL%,%PROCESSOR_REVISION%

These variables contain details of theCPU; they are set during system installation.

%PUBLIC%

The%PUBLIC% variable (introduced with Vista) points to thePublic (pseudo) user profile directory "C:\Users\Public".

%ProgramFiles%,%ProgramFiles(x86)%,%ProgramW6432%

The%ProgramFiles% variable points to theProgram Files directory, which stores all the installed programs of Windows and others. The default on English-language systems is "C:\Program Files". In 64-bit editions of Windows (XP, 2003, Vista), there are also%ProgramFiles(x86)%, which defaults to "C:\Program Files (x86)", and%ProgramW6432%, which defaults to "C:\Program Files". The%ProgramFiles% itself depends on whether the process requesting the environment variable is itself 32-bit or 64-bit (this is caused byWindows-on-Windows 64-bit redirection^[28]).

%CommonProgramFiles%,%CommonProgramFiles(x86)%,%CommonProgramW6432%

This variable points to theCommon Files subdirectory of theProgram Files directory. The default on English-language systems is "C:\Program Files\Common Files". In 64-bit editions of Windows (XP, 2003, Vista), there are also%ProgramFiles(x86)%, which defaults to "C:\Program Files (x86)", and%ProgramW6432%, which defaults to "C:\Program Files". The%ProgramFiles% itself depends on whether the process requesting the environment variable is itself 32-bit or 64-bit (this is caused byWindows-on-Windows 64-bit redirection).

%OneDrive%

The%OneDrive% variable is a special system-wide environment variable found on Windows NT and its derivatives. Its value is the path of where (if installed and setup) the Onedrive directory is located. The value of%OneDrive% is in most cases "C:\Users\{Username}\OneDrive\".

%SystemDrive%

The%SystemDrive% variable is a special system-wide environment variable found on Windows NT and its derivatives. Its value is the drive upon which the system directory was placed. The value of%SystemDrive% is in most cases "C:".

%SystemRoot%

The%SystemRoot% variable is a special system-wide environment variable found on the Windows NT family of operating systems. Its value is the location of the system directory, including the drive and path. The drive is the same as%SystemDrive% and the default path on a clean installation depends upon the version of the operating system. By default:

• Windows XP and newer versions use "\WINDOWS".
• Windows 2000,NT 4.0 andNT 3.1 use "\WINNT".
• Windows NT 3.5 andNT 3.51 uses "\WINNT35".
• Windows NT 4.0 Terminal Server uses "\WTSRV".

%windir%

This variable points to theWindows directory. (On the Windows NT family of operating systems, it is identical to the%SystemRoot% variable).Windows 95–98 andWindows ME are, by default, installed in "C:\Windows". For other versions of Windows, see the%SystemRoot% entry above.

User management variables^{[citation needed]} store information related to resources and settings owned by varioususer profiles within the system. As a general rule, these variables do not refer to critical system resources or locations that are necessary for the OS to run.

%ALLUSERSPROFILE% (%PROGRAMDATA% since Windows Vista)

This variable expands to the full path to theAll Users profile directory. This profile contains resources and settings that are used by all system accounts.Shortcut links copied to theAll Users\'Start menu orDesktop directories will appear in every user'sStart menu orDesktop, respectively.

%USERDOMAIN%

The name of theWorkgroup orWindows Domain to which the current user belongs. The related variable,%LOGONSERVER%, holds thehostname of the server that authenticated the current user's login credentials (name and password). For home PCs and PCs in a workgroup, the authenticating server is usually the PC itself. For PCs in a Windows domain, the authenticating server is adomain controller (a primary domain controller, or PDC, in Windows NT 4-based domains).

%USERPROFILE%

A special system-wide environment variable found on Windows NT and its derivatives. Its value is the location of the current user's profile directory, in which is found that user's HKCU registry hive (NTUSER). Users can also use the%USERNAME% variable to determine the active users login identification.

Optional System variables^{[citation needed]} are not explicitly specified by default but can be used to modify the default behavior of certain built-in console commands. These variables also do not need to be explicitly specified as command line arguments.

The following tables shows typical default values of certain environment variables under English versions of Windows as they can be retrieved underCMD.

(Some of these variables are also defined when runningCOMMAND.COM under Windows, but differ in certain important details: UnderCOMMAND.COM, the names of environment variable are always uppercased. Some, but not all variables contain short8.3 rather thanlong file names. While some variables present in theCMD environment are missing, there are also some variables specific to theCOMMAND environment.)

In this list, there is no environment variable that refers to the location of the user'sMy Documents directory, so there is no standard method for setting a program's home directory to be theMy Documents directory.

The command processors in DOS and Windows also support pseudo-environment variables. These are values that are fetched like environment variables, but are not truly stored in the environment but computed when requested.

Besides true environment variables, which are statically stored in the environment until changed or deleted, a number of pseudo-environment variables exist for batch processing.

The so-calledreplacement parameters orreplaceable parameters (Microsoft / IBM terminology) akareplacement variables (Digital Research / Novell / Caldera terminology)^[21] orbatch file parameters (JP Software terminology)^[10]%1..%9 and%0 can be used to retrieve the calling parameters of a batchjob, seeSHIFT. In batchjobs, they can be retrieved just like environment variables, but are not actually stored in the environment.

Some command-line processors (likeDR-DOSCOMMAND.COM,^[21]Multiuser DOSMDOS.COM/TMP.EXE (Terminal Message Process), JP Software4DOS,4OS2,4NT,Take Command and Windowscmd.exe) support a type of pseudo-environment variables namedsystem information variables (Novell / Caldera terminology)^[21] orinternal variables (JP Software terminology),^[10] which can be used to retrieve various possibly dynamic, but read-only information about the running system in batch jobs. The returned values represent the status of the system in the moment these variables are queried; that is, reading them multiple times in a row may return different values even within the same command; querying them has no direct effect on the system. Since they are not stored in the environment, they are not listed bySET and do not exist for external programs to retrieve. If a true environment variable of the same name is defined, it takes precedence over the corresponding variable until the environment variable is deleted again. They are not case-sensitive.While almost all such variables are prefixed with anunderscore ("_") by 4DOS etc. by convention (f.e.%_SECOND%),^[10] they are not under DR-DOSCOMMAND.COM (f.e.%OS_VERSION%).

In addition, 4DOS, 4OS2, 4NT, and Take Command also support so calledvariable functions,^[10] including user-definable ones. They work just likeinternal variables, but can take optional parameters (f.e.%@EVAL[]%) and may even change the system status depending on their function.

System information variables supported by DR-DOSCOMMAND.COM:

%AM_PM%

This pseudo-variable returns the ante- or post-midday status of the current time. The returned string depends on the locale-specific version of DR-DOS, f.e. "am" or "pm" in the English version. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%DAY%

This pseudo-variable returns the days of the current date in a 2-digit format with leading zeros, f.e. "01".."31". See also the similar pseudo-variable%_DAY%. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%DAY_OF_WEEK%

This pseudo-variable returns the day name of the week in a 3-character format. The returned string depends on the locale-specific version of DR-DOS, f.e. "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", or "Sat" in the English version. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%ERRORLEVEL%

InCOMMAND.COM of DR-DOS 7.02 and higher, this pseudo-variable returns the last error level returned by an external program or theRETURN command, f.e. "0".."255".^[30][31] See also the identically named pseudo-variable%ERRORLEVEL% under Windows and theIF ERRORLEVEL conditional command.

%ERRORLVL%

In DR-DOS 7.02 and higher, this pseudo-variable returns the last error level in a 3-digit format with leading zeros, f.e. "000".."255".^[30][31] UnderMultiuser DOS, this is a true environment variable automatically updated by the shell to the return code of exiting programs.^[23] See also the related pseudo-variable%ERRORLEVEL% under DR-DOS and theIF ERRORLEVEL command.

%GREETING_TIME%

This pseudo-variable returns the 3-level day greeting time. The returned string depends on the locale-specific version of DR-DOS, f.e. "morning", "afternoon", or "evening" in the English version. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%HOUR%

This pseudo-variable returns the hours of the current time in 12-hour format without leading zeros, f.e. "1".."12". It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%HOUR24%

This pseudo-variable returns the hours of the current time in 24-hour format in a 2-digit format with leading zeros, f.e. "00".."23". It resembles an identically namedidentifier variable inNovell NetWare login scripts. See also the similar pseudo-variable%_HOUR%.

%MINUTE%

This pseudo-variable returns the minutes of the current time in a 2-digit format with leading zeros, f.e "00".."59". It resembles an identically namedidentifier variable inNovell NetWare login scripts. See also the similar pseudo-variable%_MINUTE%.

%MONTH%

This pseudo-variable returns the months of the current date in a 2-digit format with leading zeros, f.e. "01".."12". It resembles an identically namedidentifier variable inNovell NetWare login scripts. See also the similar pseudo-variable%_MONTH%.

%MONTH_NAME%

This pseudo-variable returns the month name of the current date. The returned string depends on the locale-specific version of DR-DOS, f.e. "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", or "December" in the English version. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%NDAY_OF_WEEK%

This pseudo-variable returns the number of day of the current week, f.e. "1".."7" (with "1" for Sunday). It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%OS_VERSION%

This pseudo-variable returns the version of the operating system depending on the current setting of the environment variable%VER%. If%VER% is not defined,%OS_VERSION% returns "off". It resembles an identically namedidentifier variable inNovell NetWare login scripts, which may return versions also for non-DR-DOS versions of DOS.

%SECOND%

This pseudo-variable returns the seconds of the current time in a 2-digit format with leading zeros, f.e. "00".."59". It resembles an identically namedidentifier variable inNovell NetWare login scripts. See also the similar pseudo-variable%_SECOND%.

%SHORT_YEAR%

This pseudo-variable returns the year of the current date in a 2-digit format with leading zeros, f.e. "93".."99", "00".."92". It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%YEAR% and%_YEAR%

Supported sinceNovell DOS 7, the%YEAR% pseudo-variable returns the year of the current date in a 4-digit format, f.e. "1980".."2099". It resembles an identically namedidentifier variable inNovell NetWare login scripts. DR-DOS 7.02 and higher added%_YEAR% for compatibility with4DOS, returning the same value.^[10]

%/%

InCOMMAND.COM of DR-DOS 7.02 and higher, this pseudo-variable returns the currentSwitChar setting of the system, either "/" (DOS style) or "-" (Unix style).^[32][33] See also the relatedCONFIG.SYS directiveSWITCHAR and the environment variable%SWITCHAR%.

%_CODEPAGE%

This pseudo-variable returns the systems' currentcode page ("1".."65533"), f.e. "437", "850", "858". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also theCHCP command.

%_COLUMNS%

This pseudo-variable returns the current number of screen columns depending on the display mode, f.e. "40", "80", "132", etc. This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also a similar environment variable%$WIDTH% under DOS Plus.

%_COUNTRY%

This pseudo-variable returns the systems' currentcountry code ("1".."65534"), f.e. "1" for USA, "44" for UK, "49" for Germany, "20049" withISO 8601, "21049" with ISO 8601 andEuro support.^[33][34] This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also theCONFIG.SYS directiveCOUNTRY.

%_DAY%

This pseudo-variable returns the days of the current date without leading zeros, f.e. "1".."31". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also the similar pseudo-variable%DAY%.

%_HOUR%

This pseudo-variable returns the hours of the current time in 24-hour format without leading zeros, f.e. "0".."23". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also the similar pseudo-variable%HOUR24%.

%_MINUTE%

This pseudo-variable returns the minutes of the current time without leading zeros, f.e "0".."59". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also the similar pseudo-variable%MINUTE%.

%_MONTH%

This pseudo-variable returns the months of the current date without leading zeros, f.e. "1".."12". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also the similar pseudo-variable%MONTH%.

%_ROWS%

This pseudo-variable returns the current number of screen rows depending on the display mode, f.e. "25", "43", "50", etc. This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See a similar environment variable%$LENGTH% under DOS Plus.

%_SECOND%

This pseudo-variable returns the seconds of the current time without leading zeros, f.e. "0".."59". This variable was originally introduced by4DOS,^[10] but also became available withCOMMAND.COM since DR-DOS 7.02. See also the similar pseudo-variable%SECOND%.

System information variables supported by DR-DOSCOMMAND.COM with networking loaded:

%LOGIN_NAME%

This pseudo-variable returns the user name. This always worked withNETX, but it will also work withPersonal NetWare'sODI/VLM if the current drive is a PNW-mapped drive (otherwise an empty string is returned). See also the similarly named environment variable%LOGINNAME%.

%P_STATION%

This pseudo-variable returns the physical station number in a format "????????????". The value depends on theMAC address of the network adapter, but can be overridden. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%STATION%

This pseudo-variable returns the logical station number starting with "1" for the first client. The numbers are assigned by the file server and remain static for as long as theIPX connection remains established. It resembles an identically namedidentifier variable inNovell NetWare login scripts.

%FULL_NAME%

This pseudo-variable returns the full name of the logged in user, if available. It resembles an identically namedidentifier variable inNovell NetWare login scripts. See also the related pseudo-variable%LOGIN_NAME%.

Dynamic environment variables (also namedinternal variables orsystem information variables under DOS) are pseudo-environment variables supported byCMD.EXE when command-line extensions are enabled, and they expand to various discrete values whenever queried, that is, their values can change when queried multiple times even within the same command. While they can be used in batch jobs and at the prompt, they are not stored in the environment. Consequently, they are neither listed bySET nor do they exist for external programs to read. They are not case-sensitive.

Indirectly, they are also supported under Windows'COMMAND.COM, which has been modified to internally callCMD.EXE to execute the commands.

%CD%

This pseudo-variable expands to the current directory equivalent to the output of the commandCD when called without arguments. While a long filename can be returned underCMD.EXE depending on the current directory, the fact that the current directory will always be in8.3 format underCOMMAND.COM will cause it to return a short filename underCOMMAND.COM, even whenCOMMAND internally callsCMD.

%CMDCMDLINE%

This pseudo-variable expands to the original startup parameters ofCMD.EXE, f.e. "C:\Windows\system32\cmd.exe". Under Windows'COMMAND.COM, this may return something like "C:\Windows\system32\cmd.exe /c ..." due to the fact thatCOMMAND.COM callsCMD.EXE internally.

%CMDEXTVERSION%

This pseudo-variable expands to the version of the command-line extensions ofCMD.EXE, if enabled (e.g. "1" underWindows NT, "2" underWindows 2000 andWindows XP).

%DATE%

This pseudo-variable expands to the current date. The date is displayed according to the current user'sdate format preferences.

%ERRORLEVEL%

This pseudo-variable expands to the last set error level, a value between "0" and "255" (without leading zeros).^[30][35][31] External commands and some internal commands set error levels upon execution. See also the identically named pseudo-variable%ERRORLEVEL% under DR-DOS and theIF ERRORLEVEL command.

%HIGHESTNUMANODENUMBER%

This pseudo-variable returns the number of the highestNUMA node.

%RANDOM%

This pseudo-variable returns a random number between "0" and "32767".

%TIME%

This pseudo-variable returns the current time. The time is displayed according to the current user's time format preferences. If the%TIME% and%DATE% variables are both used, it is important to read them both in this particular order in rapid succession in order to avoid midnight-rollover problems.

Unix-like shells have similar dynamically generated variables, bash's$RANDOM being a well-known example. However, since these shells have a concept of local variables, they are described as special local variables instead.^[36]

• Variable (computer science)
• List of POSIX commands
• List of DOS commands
• Special folder
• Environment Modules
• PWB shell
• Windows Registry

• Chen, Raymond (2010-05-06)."What are these strange =C: environment variables?".The New Old Thing.Microsoft. Retrieved2025-04-03.

• environ(7): user environment – Linux Programmer'sManual – Overview, Conventions and Miscellanea
• environ(7) – FreeBSD Miscellaneous InformationManual
• environ(7) – Darwin andmacOS Miscellaneous InformationManual
• environ(7) – Solaris 11.4 Standards, Environments, Macros, Character Sets, and Miscellany ReferenceManual
• "Environment Variables Wiki". Archived fromthe original on 2019-04-27.
• User Environment Variables
• fix setx.exe not found bug

• Windows commands
• Operating system technology
• Environment variables

• CS1 errors: periodical ignored
• CS1 German-language sources (de)
• Webarchive template archiveis links
• Articles needing additional references from May 2023
• All articles needing additional references
• Articles with short description
• Short description is different from Wikidata
• Use dmy dates from April 2019
• Use list-defined references from January 2022
• All articles with unsourced statements
• Articles with unsourced statements from August 2014