Lines Matching refs:file
145 written to disk and which file write it was. This can
159 :earlier {N}f Go to older text state {N} file writes before.
164 When at the state of the first file write, or when
165 the file was not written, ":earlier 1f" will go to
178 :later {N}f Go to newer text state {N} file writes later.
179 When at the state of the last file write, ":later 1f"
236 your undo history when you write a file and restore undo history when you edit
237 the file again.
239 The 'undofile' option is checked after writing a file, before the BufWritePost
244 Vim saves undo trees in a separate undo file, one for each edited file, using
246 detect if an undo file is no longer synchronized with the file it was written
247 for (with a hash of the file contents) and ignore it when the file was changed
248 after the undo file was written, to prevent corruption. An undo file is also
249 ignored if its owner differs from the owner of the edited file, except when
250 the owner of the undo file is the current user. Set 'verbose' to get a
251 message about that when opening a file.
253 Undo files are normally saved in the same directory as the file. This can be
256 When the file is encrypted, the text in the undo file is also crypted. The
259 Note that text properties are not stored in the undo file. You can restore
261 from an undo file. Rationale: It would require the associated text property
268 :wundo[!] {file}
269 Write undo history to {file}.
270 When {file} exists and it does not look like an undo file
271 (the magic number at the start of the file is wrong), then
273 If it exists and does look like an undo file it is
277 the existing file and then creating a new file with the same
281 :rundo {file} Read undo history from {file}.
284 history file. E.g.: >
304 You can use the |undofile()| function to find out the file name that Vim would
309 error messages, e.g., when the file cannot be read or written.
313 Reading an existing undo file may fail for several reasons:
314 *E822* It cannot be opened, because the file permissions don't allow it.
315 *E823* The magic number at the start of the file doesn't match. This usually
316 means it is not an undo file.
317 *E824* The version number of the undo file indicates that it's written by a
319 write the buffer if you want to keep the undo info in the file.
321 The file text differs from when the undo file was written. This means
322 the undo file cannot be used, it would corrupt the text. This also
323 happens when 'encoding' differs from when the undo file was written.
324 *E825* The undo file does not contain valid contents and cannot be used.
325 *E826* The undo file is encrypted but decryption failed.
326 *E827* The undo file is encrypted but this version of Vim does not support
327 encryption. Open the file with another Vim.
328 *E832* The undo file is encrypted but 'key' is not set, the text file is not
329 encrypted. This would happen if the text file was written by Vim
331 You probably want to delete this undo file.
332 "Not reading undo file, owner differs"
333 The undo file is owned by someone else than the owner of the text
334 file. For safety the undo file is not used.
336 Writing an undo file may fail for these reasons:
337 *E828* The file to be written cannot be created. Perhaps you do not have
339 "Cannot write undo file in any directory in 'undodir'"
341 "Will not overwrite with undo file, cannot read"
342 A file exists with the name of the undo file to be written, but it
343 cannot be read. You may want to delete this file or rename it.
344 "Will not overwrite, this is not an undo file"
345 A file exists with the name of the undo file to be written, but it
347 this file or rename it.
348 "Skipping undo file write, nothing to undo"
351 *E829* An error occurred while writing the undo file. You may want to try
376 that this is relative to the last write of the file. Typing "u" after ":w"