case does not matter.
@menu
-* Example: Completion Example.
-* Commands: Completion Commands.
-* Strict Completion::
-* Options: Completion Options.
+* Example: Completion Example. Examples of using completion.
+* Commands: Completion Commands. A list of completion commands.
+* Strict Completion:: Different types of completion.
+* Options: Completion Options. Options for completion.
@end menu
@node Completion Example
@code{history-length} is @code{t}, though, there is no maximum length
and elements are never deleted.
+@vindex history-delete-duplicates
+ The variable @code{history-delete-duplicates} specifies whether to
+delete duplicates in history. If the value of @code{history-delete-duplicates}
+is @code{t}, that means when adding a new history element, all
+previous identical elements are deleted.
+
@node Repetition
@section Repeating Minibuffer Commands
@cindex command history
you can edit its expression as usual and then resubmit it by typing
@key{RET} as usual.
-@vindex isearch-resume-enabled
+@vindex isearch-resume-in-command-history
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}.
+but it does something similar. Although it behaves like a complex command,
+it normally does not appear in the history list for @kbd{C-x
+@key{ESC} @key{ESC}}. You can make it appear in the history by
+setting @code{isearch-resume-in-command-history} to a non-@code{nil}
+value.
@vindex command-history
The list of previous minibuffer-using commands is stored as a Lisp