aboutsummaryrefslogtreecommitdiff
path: root/doc/write_mkpath.txt
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2019-06-01 18:09:09 +1200
committerTom Ryder <tom@sanctum.geek.nz>2019-06-01 18:09:09 +1200
commitb34b8a2b3131c760599f4217a185ebd51d9e4e28 (patch)
tree3bed66f8921aadc1ccabae5a4e97f4ba50839627 /doc/write_mkpath.txt
parentMerge branch 'hotfix/v1.1.2' into develop (diff)
downloadvim-write-mkpath-b34b8a2b3131c760599f4217a185ebd51d9e4e28.tar.gz
vim-write-mkpath-b34b8a2b3131c760599f4217a185ebd51d9e4e28.zip
Throw away the path absolution hooks
Too awkward, not worth it, especially the mess it makes of alternate files.
Diffstat (limited to 'doc/write_mkpath.txt')
-rw-r--r--doc/write_mkpath.txt9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/write_mkpath.txt b/doc/write_mkpath.txt
index 3416629..9424184 100644
--- a/doc/write_mkpath.txt
+++ b/doc/write_mkpath.txt
@@ -20,12 +20,9 @@ This plugin only loads if 'compatible' is not set.
CAVEATS *write_mkpath-caveats*
-In Vim 7.0 and 7.1, the path will be created relative to Vim's working
-directory at the time of the write operation, which might not be the same as
-the working directory when the buffer was first created, e.g. after a |:cd|
-change. This is worked around safely in Vim 7.2 and newer by calculating an
-absolute path for new buffers with nonexistent relative paths, but filename
-escaping bugs in earlier versions preclude the same fix in older versions.
+The path will be created relative to Vim's working directory at the time of
+the write operation, which might not be the same as the working directory when
+the buffer was first created, e.g. after a |:cd| change.
AUTHOR *write_mkpath-author*