这个相对路径到绝对路径转换器的壳函数

不需要任何工具(只需要CD和pwd) 适用于目录和文件 处理. .和。 处理目录或文件名中的空格 要求文件或目录存在 如果给定路径上不存在，则返回零 将绝对路径作为输入处理(基本上是传递它们)

代码:

function abspath() {
    # generate absolute path from relative path
    # $1     : relative filename
    # return : absolute path
    if [ -d "$1" ]; then
        # dir
        (cd "$1"; pwd)
    elif [ -f "$1" ]; then
        # file
        if [[ $1 = /* ]]; then
            echo "$1"
        elif [[ $1 == */* ]]; then
            echo "$(cd "${1%/*}"; pwd)/${1##*/}"
        else
            echo "$(pwd)/$1"
        fi
    fi
}

示例:

# assume inside /parent/cur
abspath file.txt        => /parent/cur/file.txt
abspath .               => /parent/cur
abspath ..              => /parent
abspath ../dir/file.txt => /parent/dir/file.txt
abspath ../dir/../dir   => /parent/dir          # anything cd can handle
abspath doesnotexist    =>                      # empty result if file/dir does not exist
abspath /file.txt       => /file.txt            # handle absolute path input

注意:这是基于nolan6000和bsingh的答案，但修复了文件大小写。

我也理解最初的问题是关于一个现有的命令行实用程序。但由于这似乎是关于stackoverflow的问题，包括shell脚本，希望有最小的依赖关系，我把这个脚本解决方案放在这里，所以我可以稍后找到它:)

$ readlink -m FILE
/path/to/FILE

这比readlink -e FILE或realpath更好，因为即使文件不存在，它也能工作。

这里有一个只使用zsh的函数，我喜欢它的紧凑性。它使用了“A”扩展修饰符—参见zshexpn(1)。

realpath() { for f in "$@"; do echo ${f}(:A); done }

我已经在我的系统上放置了以下脚本&当我想快速获取当前目录下文件的完整路径时，我将其称为bash别名:

#!/bin/bash
/usr/bin/find "$PWD" -maxdepth 1 -mindepth 1 -name "$1"

我不知道为什么，但是，在OS X上，当被脚本“$PWD”调用时，扩展到绝对路径。当在命令行上调用find命令时，它不会执行。但这是我想要的…享受。

通常不存在文件的绝对路径(这句话的意思是通常可能有多个路径，因此使用定冠词the是不合适的)。绝对路径是从根“/”开始的任何路径，并且与工作目录无关地指定文件。(参见维基百科)。

相对路径是从另一个目录开始解释的路径。如果它是应用程序操作的相对路径，则它可能是工作目录 (虽然不一定)。当它位于目录中的符号链接中时，通常打算相对于该目录(尽管用户可能有其他用途)。

因此，绝对路径只是相对于根目录的路径。

A path (absolute or relative) may or may not contain symbolic links. If it does not, it is also somewhat impervious to changes in the linking structure, but this is not necessarily required or even desirable. Some people call canonical path ( or canonical file name or resolved path) an absolute path in which all symbolic links have been resolved, i.e. have been replaced by a path to whetever they link to. The commands realpath and readlink both look for a canonical path, but only realpath has an option for getting an absolute path without bothering to resolve symbolic links (along with several other options to get various kind of paths, absolute or relative to some directory).

这里有几点需要说明:

symbolic links can only be resolved if whatever they are supposed to link to is already created, which is obviously not always the case. The commands realpath and readlink have options to account for that. a directory on a path can later become a symbolic link, which means that the path is no longer canonical. Hence the concept is time (or environment) dependent. even in the ideal case, when all symbolic links can be resolved, there may still be more than one canonical path to a file, for two reasons: the partition containing the file may have been mounted simultaneously (ro) on several mount points. there may be hard links to the file, meaning essentially the the file exists in several different directories.

因此，即使使用更严格的规范路径定义，一个文件也可能有多个规范路径。这也意味着限定符规范是不适当的，因为它通常意味着唯一性的概念。

这将在Bash上回答另一个类似问题时扩展对该主题的简短讨论:检索给定相对的绝对路径

我的结论是，realpath比readlink设计得更好，也更灵活。 readlink唯一没有被realpath覆盖的用法是没有返回符号链接值的选项的调用。

使用realpath

$ realpath example.txt
/home/username/example.txt