aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/emacs/files.texi16
1 files changed, 7 insertions, 9 deletions
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index ac072dbeaa5..3c338fcdfe6 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -247,15 +247,13 @@ changes and save them, the file is created.
247 247
248@cindex minibuffer confirmation 248@cindex minibuffer confirmation
249@cindex confirming in the minibuffer 249@cindex confirming in the minibuffer
250 When you attempt to visit a new file, Emacs might prompt you for 250 When @key{TAB} completion results in a nonexistent file name and you
251confirmation first, in case you entered the wrong file name. Emacs 251type @key{RET} immediately to visit it, Emacs asks for confirmation
252asks for confirmation only if the last key you typed in the 252because it is quite possible that you expected completion to go
253minibuffer, before submitting the input with @key{RET}, was @key{TAB} 253further and give you an existing file's name. Type @key{RET} to
254(@code{minibuffer-complete}). This catches a common mistake, in which 254confirm and visit the nonexistent file. The string @samp{[Confirm]}
255one types @key{RET} before realizing that @key{TAB} did not complete 255appears for a short time after the file name to indicate the need to
256far enough to yield a desired file name (@pxref{Completion}). Emacs 256confirm in this way.
257asks for confirmation by putting the message @samp{[Confirm]} in the
258minibuffer; type @key{RET} again to confirm and visit the file.
259 257
260@vindex confirm-nonexistent-file-or-buffer 258@vindex confirm-nonexistent-file-or-buffer
261 The variable @code{confirm-nonexistent-file-or-buffer} controls 259 The variable @code{confirm-nonexistent-file-or-buffer} controls