X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/eb9ee0dbe65d9166b86d539a764205ba439e3965..690a6d089ad61ded63d9532fbc7268f91355bea3:/man/mini.texi

diff --git a/man/mini.texi b/man/mini.texi
index 3f4487b834..88aac3bdc7 100644
--- a/man/mini.texi
+++ b/man/mini.texi
@@ -82,9 +82,9 @@ Find File: /u2/emacs/src/
 @end example
 
 @noindent
-where @samp{Find File:@: } is the prompt.  Typing @kbd{buffer.c}
-specifies the file @file{/u2/emacs/src/buffer.c}.  To find files in
-nearby directories, use @kbd{..}; thus, if you type
+where @samp{Find File:@: } is the prompt.  Typing @kbd{buffer.c} as
+input specifies the file @file{/u2/emacs/src/buffer.c}.  To find files
+in nearby directories, use @kbd{..}; thus, if you type
 @kbd{../lisp/simple.el}, you will get the file named
 @file{/u2/emacs/lisp/simple.el}.  Alternatively, you can kill with
 @kbd{M-@key{DEL}} the directory names you don't want (@pxref{Words}).
@@ -184,7 +184,7 @@ argument, then Emacs visibly fills in the rest, or as much as
 can be determined from the part you have typed.
 
   When completion is available, certain keys---@key{TAB}, @key{RET}, and
-@key{SPC}---are rebound to complete the text present in the minibuffer
+@key{SPC}---are rebound to complete the text in the minibuffer before point
 into a longer string that it stands for, by matching it against a set of
 @dfn{completion alternatives} provided by the command reading the
 argument.  @kbd{?} is defined to display a list of possible completions
@@ -192,7 +192,7 @@ of what you have inserted.
 
   For example, when @kbd{M-x} uses the minibuffer to read the name of a
 command, it provides a list of all available Emacs command names to
-complete against.  The completion keys match the text in the minibuffer
+complete against.  The completion keys match the minibuffer text
 against all the command names, find any additional name characters
 implied by the ones already present in the minibuffer, and add those
 characters to the ones you have given.  This is what makes it possible
@@ -245,10 +245,10 @@ when completion is available.
 
 @table @kbd
 @item @key{TAB}
-Complete the text in the minibuffer as much as possible
+Complete the text before point in the minibuffer as much as possible
 (@code{minibuffer-complete}).
 @item @key{SPC}
-Complete the minibuffer text, but don't go beyond one word
+Complete the minibuffer text before point, but don't go beyond one word
 (@code{minibuffer-complete-word}).
 @item @key{RET}
 Submit the text in the minibuffer as the argument, possibly completing
@@ -363,6 +363,14 @@ However, if @emph{all} the possible completions end in ``ignored''
 strings, then they are not ignored.  Ignored extensions do not apply to
 lists of completions---those always mention all possible completions.
 
+  If an element of the list in @code{completion-ignored-extensions} ends
+in a slash @file{/}, it indicates a subdirectory that should be ignored
+when completing file names.  (Elements of
+@code{completion-ignored-extensions} which do not end in a slash are
+never considered when a completion candidate is a directory; thus,
+completion returns directories whose names end in @file{.elc} even
+though there's an element @code{".elc"} in the list.)
+
 @vindex completion-auto-help
   Normally, a completion command that cannot determine even one
 additional character automatically displays a list of all possible
@@ -550,6 +558,13 @@ of saved entire commands.  After finding the desired previous command,
 you can edit its expression as usual and then resubmit it by typing
 @key{RET} as usual.
 
+@vindex isearch-resume-enabled
+  Incremental search does not, strictly speaking, use the minibuffer,
+but it does something similar, so normally it is treated as a complex
+command and it appears in the history list for @kbd{C-x @key{ESC}
+@key{ESC}}.  You can disable that by setting
+@code{isearch-resume-enabled} to @code{nil}.
+
 @vindex command-history
   The list of previous minibuffer-using commands is stored as a Lisp
 list in the variable @code{command-history}.  Each element is a Lisp