From df7b97d99dc30020ea8535b12c79f63e1edb4628 Mon Sep 17 00:00:00 2001 From: Fabian Boehm Date: Mon, 8 Aug 2022 21:12:37 +0200 Subject: [PATCH] Link to correct path subcommand Resolve is indeed the same as resolve --- doc_src/cmds/path.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc_src/cmds/path.rst b/doc_src/cmds/path.rst index 5bc22a797..b17c7203e 100644 --- a/doc_src/cmds/path.rst +++ b/doc_src/cmds/path.rst @@ -316,7 +316,7 @@ Examples It is similar to ``realpath``, as it creates the "real", canonical version of the path. However, for paths that can't be resolved, e.g. if they don't exist or form a symlink loop, it will resolve as far as it can and normalize the rest. -Because it resolves symlinks, it works sort of like ``pwd -P``. E.g. ``path resolve link/..`` will return the parent directory of what the link points to, just like ``cd link; cd (pwd -P)/..`` would go to it. For a logical view of the filesystem, see ``path resolve``. +Because it resolves symlinks, it works sort of like ``pwd -P``. E.g. ``path resolve link/..`` will return the parent directory of what the link points to, just like ``cd link; cd (pwd -P)/..`` would go to it. For a logical view of the filesystem, see ``path normalize``. It returns 0 if any normalization or resolution was done, i.e. any given path wasn't in canonical form.