diff options
author | Bram Moolenaar <Bram@vim.org> | 2014-03-23 16:04:02 +0100 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2014-03-23 16:04:02 +0100 |
commit | 5803ae6c076b1d61381afe27fcdedac61dd2cda9 (patch) | |
tree | d900239b97e5126bf6ae85fb0a9b05a531dcc7b8 /runtime | |
parent | f7ff6e85e8a4e84cff023f5db4b66ef85986605a (diff) |
updated for version 7.4.213v7.4.213
Problem: It's not possible to open a new buffer without creating a swap
file.
Solution: Add the ":noswapfile" modifier. (Christian Brabandt)
Diffstat (limited to 'runtime')
-rw-r--r-- | runtime/doc/recover.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/runtime/doc/recover.txt b/runtime/doc/recover.txt index 5fc09c0e72..650feb208b 100644 --- a/runtime/doc/recover.txt +++ b/runtime/doc/recover.txt @@ -81,7 +81,14 @@ the amount of memory used to be higher than given with 'maxmem' or 'maxmemtot'. And when making a change to a read-only file, the swap file is created anyway. -The 'swapfile' option can be reset to avoid creating a swapfile. +The 'swapfile' option can be reset to avoid creating a swapfile. And the +|:noswapfile| modifier can be used to not create a swapfile for a new buffer. + +:noswap[file] {command} *:noswap* *:noswapfile* + Execute {command}. If it contains a command that loads a new + buffer, it will be loaded without creating a swapfile and the + 'swapfile' option will be reset. If a buffer already had a + swapfile it is not removed and 'swapfile' is not reset. Detecting an existing swap file ~ |