From a4988bb3cd2d69ce3c934c2a1cf8aa7b16bab29b Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Sun, 2 Nov 2025 07:11:20 +0800 Subject: [PATCH] vim-patch:213109a: runtime(doc): clarify W11 warning and possible options (#36426) fixes: vim/vim#18589 https://github.com/vim/vim/commit/213109a999c8c854c1af3bf57540e56afa23c20c Co-authored-by: Christian Brabandt --- runtime/doc/message.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/runtime/doc/message.txt b/runtime/doc/message.txt index 3960bad649..c4384aa362 100644 --- a/runtime/doc/message.txt +++ b/runtime/doc/message.txt @@ -610,6 +610,22 @@ Set the 'autoread' option if you want to do this automatically. This message is not given when 'buftype' is not empty. Also see the |FileChangedShell| autocommand. +You will be given a dialog with the following options: + +"OK": Dismiss the warning and continue editing. No changes are + loaded, the buffer remains as it is. + +"Load File": Reload the file from disk, replacing the current buffer + contents. Any changes you made in Vim that haven't been saved + will be lost. + +"Load File and Options": + Reload the file from disk and, in addition, apply relevant + file settings, such as indentation, syntax highlighting, text + width, and other filetype-specific options. This ensures the + buffer matches the file's intended configuration according to + your current settings and autocommands. + There is one situation where you get this message even though there is nothing wrong: If you save a file in Windows on the day the daylight saving time starts. It can be fixed in one of these ways: