Bash别名绝对不接受参数。我只是添加了一个别名来创建一个新的react应用程序，它接受应用程序名称作为参数。以下是我的流程：

在nano中打开bash_profile进行编辑

nano /.bash_profile

添加别名，每行一个：

alias gita='git add .'
alias gitc='git commit -m "$@"'
alias gitpom='git push origin master'
alias creact='npx create-react-app "$@"'

注意：“$@”接受传入的参数，如“创建我的新应用程序”

保存并退出nano编辑器

ctrl+o to to to write（按回车键）；ctrl+x退出

告诉终端使用.bash_profile中的新别名

source /.bash_profile

就是这样！现在可以使用新别名

实际上，函数几乎总是答案，正如手册页中的这句话所证实的：“对于几乎所有的目的，别名都被shell函数所取代。”

为了完整性，并且因为这可能是有用的（稍微更轻量级的语法），可以注意到，当参数跟随别名时，仍然可以使用它们（尽管这不能满足OP的要求）。这可能最容易用一个例子来演示：

alias ssh_disc='ssh -O stop'

允许我键入smth，如ssh_disc myhost，它按预期扩展为：ssh-O stop myhost

这对于接受复杂参数的命令很有用（我的记忆不再是以前的样子了…）

以下是示例：

alias gcommit='function _f() { git add -A; git commit -m "$1"; } ; _f'

非常重要：

｛后和｛前有一个空格。有一个；依次在每个命令之后。如果您在最后一个命令后忘记了这一点，您将看到>提示符！参数用引号括起来，如“$1”

下面是我的~/.bashrc中的三个函数示例，它们本质上是接受参数的别名：

#Utility required by all below functions.
#https://stackoverflow.com/questions/369758/how-to-trim-whitespace-from-bash-variable#comment21953456_3232433
alias trim="sed -e 's/^[[:space:]]*//g' -e 's/[[:space:]]*\$//g'"

.

:<<COMMENT
    Alias function for recursive deletion, with are-you-sure prompt.

    Example:
        srf /home/myusername/django_files/rest_tutorial/rest_venv/

    Parameter is required, and must be at least one non-whitespace character.

    Short description: Stored in SRF_DESC

    With the following setting, this is *not* added to the history:
        export HISTIGNORE="*rm -r*:srf *"
    - https://superuser.com/questions/232885/can-you-share-wisdom-on-using-histignore-in-bash

    See:
    - y/n prompt: https://stackoverflow.com/a/3232082/2736496
    - Alias w/param: https://stackoverflow.com/a/7131683/2736496
COMMENT
#SRF_DESC: For "aliaf" command (with an 'f'). Must end with a newline.
SRF_DESC="srf [path]: Recursive deletion, with y/n prompt\n"
srf()  {
    #Exit if no parameter is provided (if it's the empty string)
        param=$(echo "$1" | trim)
        echo "$param"
        if [ -z "$param" ]  #http://tldp.org/LDP/abs/html/comparison-ops.html
        then
          echo "Required parameter missing. Cancelled"; return
        fi

    #Actual line-breaks required in order to expand the variable.
    #- https://stackoverflow.com/a/4296147/2736496
    read -r -p "About to
    sudo rm -rf \"$param\"
Are you sure? [y/N] " response
    response=${response,,}    # tolower
    if [[ $response =~ ^(yes|y)$ ]]
    then
        sudo rm -rf "$param"
    else
        echo "Cancelled."
    fi
}

.

:<<COMMENT
    Delete item from history based on its line number. No prompt.

    Short description: Stored in HX_DESC

    Examples
        hx 112
        hx 3

    See:
    - https://unix.stackexchange.com/questions/57924/how-to-delete-commands-in-history-matching-a-given-string
COMMENT
#HX_DESC: For "aliaf" command (with an 'f'). Must end with a newline.
HX_DESC="hx [linenum]: Delete history item at line number\n"
hx()  {
    history -d "$1"
}

.

:<<COMMENT
    Deletes all lines from the history that match a search string, with a
    prompt. The history file is then reloaded into memory.

    Short description: Stored in HXF_DESC

    Examples
        hxf "rm -rf"
        hxf ^source

    Parameter is required, and must be at least one non-whitespace character.

    With the following setting, this is *not* added to the history:
        export HISTIGNORE="*hxf *"
    - https://superuser.com/questions/232885/can-you-share-wisdom-on-using-histignore-in-bash

    See:
    - https://unix.stackexchange.com/questions/57924/how-to-delete-commands-in-history-matching-a-given-string
COMMENT
#HXF_DESC: For "aliaf" command (with an 'f'). Must end with a newline.
HXF_DESC="hxf [searchterm]: Delete all history items matching search term, with y/n prompt\n"
hxf()  {
    #Exit if no parameter is provided (if it's the empty string)
        param=$(echo "$1" | trim)
        echo "$param"
        if [ -z "$param" ]  #http://tldp.org/LDP/abs/html/comparison-ops.html
        then
          echo "Required parameter missing. Cancelled"; return
        fi

    read -r -p "About to delete all items from history that match \"$param\". Are you sure? [y/N] " response
    response=${response,,}    # tolower
    if [[ $response =~ ^(yes|y)$ ]]
    then
        #Delete all matched items from the file, and duplicate it to a temp
        #location.
        grep -v "$param" "$HISTFILE" > /tmp/history

        #Clear all items in the current sessions history (in memory). This
        #empties out $HISTFILE.
        history -c

        #Overwrite the actual history file with the temp one.
        mv /tmp/history "$HISTFILE"

        #Now reload it.
        history -r "$HISTFILE"     #Alternative: exec bash
    else
        echo "Cancelled."
    fi
}

参考文献：

从字符串中删除空白：如何从Bash变量中删除空白？实际换行符：https://stackoverflow.com/a/4296147/2736496别名w/param：https://stackoverflow.com/a/7131683/2736496（这个问题的另一个答案）组氨酸：https://superuser.com/questions/232885/can-you-share-wisdom-on-using-histignore-in-bashY/N提示：https://stackoverflow.com/a/3232082/2736496从历史记录中删除所有匹配项：https://unix.stackexchange.com/questions/57924/how-to-delete-commands-in-history-matching-a-given-string字符串是否为空：http://tldp.org/LDP/abs/html/comparison-ops.html

函数和别名都可以使用其他函数和别名所示的参数。此外，我想指出几个其他方面：

1.函数在自己的作用域中运行，别名共享作用域

在需要隐藏或暴露某些内容的情况下，了解这种差异可能很有用。它还表明，函数是封装的更好选择。

function tfunc(){
    GlobalFromFunc="Global From Func" # Function set global variable by default
    local FromFunc="onetwothree from func" # Set a local variable

}

alias talias='local LocalFromAlias="Local from Alias";  GlobalFromAlias="Global From Alias" # Cant hide a variable with local here '
# Test variables set by tfunc
tfunc # call tfunc
echo $GlobalFromFunc # This is visible
echo $LocalFromFunc # This is not visible
# Test variables set by talias
# call talias
talias
echo $GlobalFromAlias # This is invisible
echo $LocalFromAlias # This variable is unset and unusable 

输出：

bash-3.2$     # Test variables set by tfunc
bash-3.2$     tfunc # call tfunc
bash-3.2$     echo $GlobalFromFunc # This is visible
Global From Func
bash-3.2$     echo $LocalFromFunc # This is not visible

bash-3.2$     # Test variables set by talias
bash-3.2$     # call talias
bash-3.2$     talias
bash: local: can only be used in a function
bash-3.2$     echo $GlobalFromAlias # This is invisible
Global From Alias
bash-3.2$ echo $LocalFromAlias # This variable is unset and unusable

2.包装脚本是更好的选择

在我身上发生过几次，当通过ssh登录或涉及切换用户名或多用户环境时，找不到别名或函数。源点文件有一些提示和技巧，或者这个有趣的别名：aliassd='sudo'让这个后续的别名aliasinstall='sd-apt-get-install'按预期工作（注意sd='udo'中的额外空间）。然而，在这种情况下，包装脚本比函数或别名更有效。包装器脚本的主要优点是它在预期路径（即/usr/loca/bin/）下是可见的/可执行的，其中作为函数/别名需要在其可用之前获取。例如，您将一个函数放在~/.bash_profile或~/.bahrc中用于bash，但稍后切换到另一个shell（即zsh），则该函数不再可见。因此，当您有疑问时，包装脚本始终是最可靠和可移植的解决方案。

Bash别名不直接接受参数。您必须创建一个函数。

alias不接受参数，但可以像别名一样调用函数。例如：

myfunction() {
    #do things with parameters like $1 such as
    mv "$1" "$1.bak"
    cp "$2" "$1"
}


myfunction old.conf new.conf #calls `myfunction`

顺便说一句，.bashrc和其他文件中定义的Bash函数可以作为shell中的命令使用。例如，您可以这样调用前面的函数

$ myfunction original.conf my.conf