您所要做的就是在别名中生成一个函数：

$ alias mkcd='_mkcd(){ mkdir "$1"; cd "$1";}; _mkcd'
             ^        *      ^  ^     ^  ^         ^

您必须在“$1”周围加双引号，因为单引号不起作用。这是因为在标有箭头的地方出现引号冲突会混淆系统。此外，在标有星号的位置需要一个空间用于该功能。

为了尊重那些说你不能在别名中间插入参数的人，我刚刚测试了它，发现它确实有效。

alias mycommand = "python3 "$1" script.py --folderoutput RESULTS/"

然后，当我运行mycommandfoobar时，它的工作方式就好像我用长手键入了命令一样。

具有子命令的解决方案：

d () {
    if [ $# -eq 0 ] ; then
        docker
        return 0
    fi
    CMD=$1
    shift

    case $CMD in
    p)
        docker ps --all $@
        ;;
    r)
        docker run --interactive --tty $@
        ;;
    rma)
        docker container prune
        docker image prune --filter "dangling=true"
        ;;
    *)
        docker $CMD $@
        ;;
    esac
    return $?
}

使用：

$ d r my_image ...

打电话：

docker run --interactive --tty my_image ...

下面是我的~/.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

有正当的技术理由想要一个通用的解决方案来解决bash别名不具有重新定位任意参数的机制的问题。其中一个原因是，您希望执行的命令是否会受到执行函数所导致的环境更改的不利影响。在所有其他情况下，应使用函数。

最近迫使我尝试解决这个问题的是，我想创建一些简短的命令来打印变量和函数的定义。所以我为此写了一些函数。但是，有些变量是（或可能）由函数调用本身更改的。其中包括：

函数名称BASH_源巴什利诺BASH_ARGCBASH_ARGV

我一直在使用的基本命令（在函数中）来打印变量defns。set命令输出的形式为：

sv () { set | grep --color=never -- "^$1=.*"; }

例如。：

> V=voodoo
sv V
V=voodoo

问题：这不会打印上面提到的变量的定义，因为它们在当前上下文中，例如，如果在交互式shell提示符中（或不在任何函数调用中），FUNCNAME没有定义。但我的函数告诉我错误的信息：

> sv FUNCNAME
FUNCNAME=([0]="sv")

我提出的一个解决方案已经在其他关于这个主题的帖子中被提及。对于打印变量defns.的特定命令。，这只需要一个论点，我这样做了：

alias asv='(grep -- "^$(cat -)=.*" <(set)) <<<'

给出正确的输出（无）和结果状态（假）：

> asv FUNCNAME
> echo $?
1

然而，我仍然觉得有必要找到一个适用于任意数量的论点的解决方案。

向Bash别名命令传递任意参数的通用解决方案：

# (I put this code in a file "alias-arg.sh"):

# cmd [arg1 ...] – an experimental command that optionally takes args,
# which are printed as "cmd(arg1 ...)"
#
# Also sets global variable "CMD_DONE" to "true".
#
cmd () { echo "cmd($@)"; declare -g CMD_DONE=true; }

# Now set up an alias "ac2" that passes to cmd two arguments placed
# after the alias, but passes them to cmd with their order reversed:
#
# ac2 cmd_arg2 cmd_arg1 – calls "cmd" as: "cmd cmd_arg1 cmd_arg2"
#
alias ac2='
    # Set up cmd to be execed after f() finishes:
    #
    trap '\''cmd "${CMD_ARGV[1]}" "${CMD_ARGV[0]}"'\'' SIGUSR1;
    #        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    #       (^This is the actually execed command^)
    #
    # f [arg0 arg1 ...] – acquires args and sets up trap to run cmd:
    f () {
        declare -ag CMD_ARGV=("$@");  # array to give args to cmd
        kill -SIGUSR1 $$;             # this causes cmd to be run
        trap SIGUSR1;                 # unset the trap for SIGUSR1
        unset CMD_ARGV;               # clean up env...
        unset f;                      # incl. this function!
    };
    f'  # Finally, exec f, which will receive the args following "ac2".

例如。：

> . alias-arg.sh
> ac2 one two
cmd(two one)
>
> # Check to see that command run via trap affects this environment:
> asv CMD_DONE
CMD_DONE=true

这个解决方案的一个优点是，在编写被捕获的命令时，所有用于处理命令的位置参数（参数）的特殊技巧都将发挥作用。唯一的区别是必须使用数组语法。

例如。，

如果需要“$@”，请使用“${CMD_ARGV[@]}”。

如果需要“$#”，请使用“${#CMD_ARGV[@]}”。

Etc.

正如其他人已经指出的，使用函数应被视为最佳实践。

然而，这里有另一种方法，利用xargs：

alias junk="xargs -I "{}" -- mv "{}" "~/.Trash" <<< "

注意，这会对流的重定向产生副作用。