diff options
| author | Bram Moolenaar <Bram@vim.org> | 2019-02-10 23:18:53 +0100 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2019-02-10 23:18:53 +0100 |
| commit | dce1e89be4675bcdbc9785584d3da25295481e63 (patch) | |
| tree | bf5df09169e99ed6f60d67e2da4c4d29569d18a2 /runtime | |
| parent | 3615abb693ab2d9374ae72f0993128e32ffa3e1c (diff) | |
patch 8.1.0894: MS-Windows: resolve() does not return a reparse pointv8.1.0894
Problem: MS-Windows: resolve() does not return a reparse point.
Solution: Improve resolve(). (Yasuhiro Matsumoto, closes #3896)
Diffstat (limited to 'runtime')
| -rw-r--r-- | runtime/doc/eval.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index 0fc249c8b2..c2150e5b90 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -7385,6 +7385,9 @@ repeat({expr}, {count}) *repeat()* resolve({filename}) *resolve()* *E655* On MS-Windows, when {filename} is a shortcut (a .lnk file), returns the path the shortcut points to in a simplified form. + When {filename} is a symbolic link or junction point, return + the full path to the target. If the target of junction is + removed, return {filename}. On Unix, repeat resolving symbolic links in all path components of {filename} and return the simplified result. To cope with link cycles, resolving of symbolic links is |