So many answers, all plausible, each with pro's and con's & slightly differeing objectives (which should probably be stated for each). Here's another solution that meets a primary objective of both being clear and working across all systems, on all bash (no assumptions about bash versions, or readlink or pwd options), and reasonably does what you'd expect to happen (eg, resolving symlinks is an interesting problem, but isn't usually what you actually want), handle edge cases like spaces in paths, etc., ignores any errors and uses a sane default if there are any issues.

每个组件都存储在一个单独的变量中，您可以单独使用:

# script path, filename, directory
PROG_PATH=${BASH_SOURCE[0]}      # this script's name
PROG_NAME=${PROG_PATH##*/}       # basename of script (strip path)
PROG_DIR="$(cd "$(dirname "${PROG_PATH:-$PWD}")" 2>/dev/null 1>&2 && pwd)"

这应该能奏效:

echo `pwd`/`dirname $0`

它可能看起来很丑，这取决于它是如何被调用和cwd，但应该得到你需要去的地方(或者你可以调整字符串，如果你关心它的外观)。

假设您正在使用bash

#!/bin/bash

current_dir=$(pwd)
script_dir=$(dirname "$0")

echo $current_dir
echo $script_dir

这个脚本应该打印您所在的目录，然后是脚本所在的目录。例如，当使用/home/mez/中的脚本从/调用它时，它输出

/
/home/mez

请记住，当从命令的输出为变量赋值时，请将命令包装在$(and)中—否则将得不到所需的输出。

如果你想获得实际的脚本目录(不管你是使用符号链接还是直接调用脚本)，尝试:

BASEDIR=$(dirname $(realpath "$0"))
echo "$BASEDIR"

这在linux和macOS上都适用。我没看到有人提到realpath。不确定这种方法是否有任何缺点。

在macOS上，需要安装coreutils才能使用realpath。例如:brew install coreutils。

灵感来自blueyed的回答

read < <(readlink -f $0 | xargs dirname)
cd $REPLY

如果您正在使用bash....

#!/bin/bash

pushd $(dirname "${0}") > /dev/null
basedir=$(pwd -L)
# Use "pwd -P" for the path without links. man bash for more info.
popd > /dev/null

echo "${basedir}"