The Open Group Base Specifications Issue 8
IEEE Std 1003.1-2024
Copyright © 2001-2024 The IEEE and The Open Group

NAME

alias — define or display aliases

SYNOPSIS

alias [alias-name[=string]...]

DESCRIPTION

The alias utility shall create or redefine alias definitions or write the values of existing alias definitions to standard output. An alias definition provides a string value that shall replace a command name when it is encountered. For information on valid string values, and the processing involved, see 2.3.1 Alias Substitution .

An alias definition shall affect the current shell execution environment and the execution environments of the subshells of the current shell. When used as specified by this volume of POSIX.1-2024, the alias definition shall not affect the parent process of the current shell nor any utility environment invoked by the shell; see 2.13 Shell Execution Environment .

OPTIONS

None.

OPERANDS

The following operands shall be supported:

alias-name
Write the alias definition to standard output.
alias-name=string

Assign the value of string to the alias alias-name.

If no operands are given, all alias definitions shall be written to standard output.

STDIN

Not used.

INPUT FILES

None.

ENVIRONMENT VARIABLES

The following environment variables shall affect the execution of alias:

LANG
Provide a default value for the internationalization variables that are unset or null. (See XBD 8.2 Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
LC_ALL
If set to a non-empty string value, override the values of all the other internationalization variables.
LC_CTYPE
Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
LC_MESSAGES

Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
NLSPATH
[XSI] [Option Start] Determine the location of messages objects and message catalogs. [Option End]

ASYNCHRONOUS EVENTS

Default.

STDOUT

The format for displaying aliases (when no operands or only name operands are specified) shall be:

"%s=%s\n", name, value

The value string shall be written with appropriate quoting so that it is suitable for reinput to the shell. See the description of shell quoting in 2.2 Quoting .

STDERR

The standard error shall be used only for diagnostic messages.

OUTPUT FILES

None.

EXTENDED DESCRIPTION

None.

EXIT STATUS

The following exit values shall be returned:

 0
Successful completion.
>0
One of the name operands specified did not have an alias definition, or an error occurred.

CONSEQUENCES OF ERRORS

Default.


The following sections are informative.

APPLICATION USAGE

This utility is required to be intrinsic. See 1.7 Intrinsic Utilities for details.

Care should be taken to avoid alias values that end with a character that could be treated as part of an operator token, as it is unspecified whether the character that follows the alias name in the input can be used as part of the same token (see 2.3.1 Alias Substitution ). For example, with:

$ alias foo='echo 0'
$ foo>&2
the shell can either pass the argument '0' to echo and redirect fd 1 to fd 2, or pass no arguments to echo and redirect fd 0 to fd 2. Changing it to:
$ alias foo='echo "0"'
avoids this problem. The alternative of adding a <space> after the '0' would also avoid the problem, but in addition it would alter the way the alias works, as described in 2.3.1 Alias Substitution .

Likewise, given:

$ alias foo='some_command &'
$ foo&
the shell may combine the two '&' characters into an && (and) operator. Since the alias cannot pass arguments to some_command and thus can be expected to be invoked without arguments, adding a <space> after the '&' would be an acceptable way to prevent this. Alternatively, the alias could be specified as a grouping command:
$ alias foo='{ some_command & }'

Problems can occur for tokens other than operators as well, if the alias is used in unusual ways. For example, with:

$ alias foo='echo $'
$ foo((123))
some shells combine the '$' and the "((123))" to form an arithmetic expansion, but others do not (resulting in a syntax error).

EXAMPLES

  1. Create a short alias for a commonly used ls command:

    alias lf="ls -CF"
    
  2. Create a simple "redo" command to repeat previous entries in the command history file:

    alias r='fc -s'
    
  3. Use 1K units for du:

    alias du=du\ -k
    
  4. Set up nohup so that it can deal with an argument that is itself an alias name:

    alias nohup="nohup "
    
  5. Add the -F option to interactive uses of ls, even when executed as xargs ls or xargs -0 ls:

    alias ls='ls -F'
    alias xargs='xargs '
    alias -- -0='-0 '
    find . [...] -print | xargs ls      # breaks on filenames with \n
                                        # (two aliases expanded)
    find . [...] -print0 | xargs -0 ls  # minimizes \n issues (three
                                        # aliases expanded)
    

RATIONALE

The alias description is based on historical KornShell implementations. Known differences exist between that and the C shell. The KornShell version was adopted to be consistent with all the other KornShell features in this volume of POSIX.1-2024, such as command line editing.

Since alias affects the current shell execution environment, it is generally provided as a shell regular built-in.

Historical versions of the KornShell have allowed aliases to be exported to scripts that are invoked by the same shell. This is triggered by the alias -x flag; it is allowed by this volume of POSIX.1-2024 only when an explicit extension such as -x is used. The standard developers considered that aliases were of use primarily to interactive users and that they should normally not affect shell scripts called by those users; functions are available to such scripts.

Historical versions of the KornShell had not written aliases in a quoted manner suitable for reentry to the shell, but this volume of POSIX.1-2024 has made this a requirement for all similar output. Therefore, consistency was chosen over this detail of historical practice.

FUTURE DIRECTIONS

None.

SEE ALSO

2.9.5 Function Definition Command

XBD 8. Environment Variables

CHANGE HISTORY

First released in Issue 4.

Issue 6

This utility is marked as part of the User Portability Utilities option.

The APPLICATION USAGE section is added.

Issue 7

The alias utility is moved from the User Portability Utilities option to the Base. User Portability Utilities is now an option for interactive utilities.

SD5-XCU-ERN-97 is applied, updating the SYNOPSIS.

The first example is changed to remove the creation of an alias for a standard utility that alters its behavior to be non-conforming.

Issue 8

Austin Group Defect 854 is applied, adding a note to the APPLICATION USAGE section that this utility is required to be intrinsic.

Austin Group Defect 953 is applied, clarifying that the details of how alias replacement is performed are in the cross-referenced section ( 2.3.1 Alias Substitution ) and updating the APPLICATION USAGE section.

Austin Group Defect 1122 is applied, changing the description of NLSPATH .

Austin Group Defect 1630 is applied, adding a new item in EXAMPLES.

End of informative text.

 

return to top of page

UNIX® is a registered Trademark of The Open Group.
POSIX™ is a Trademark of The IEEE.
Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved
[ Main Index | XBD | XSH | XCU | XRAT ]