summaryrefslogtreecommitdiff
path: root/lisp
diff options
context:
space:
mode:
authorJuanma Barranquero <lekktu@gmail.com>2008-04-09 21:18:25 +0000
committerJuanma Barranquero <lekktu@gmail.com>2008-04-09 21:18:25 +0000
commite1bb0fe5aac3909859ea391087c5cef6f5e177a7 (patch)
tree3cad0b956ba2c04e1b252d5c61b3a84e90ab71a1 /lisp
parent8f49a7254d9fce4e9d6cba135c285b329d5684e9 (diff)
downloademacs-e1bb0fe5aac3909859ea391087c5cef6f5e177a7.tar.gz
(completion-auto-help): Fix typo.
Diffstat (limited to 'lisp')
-rw-r--r--lisp/minibuffer.el6
1 files changed, 3 insertions, 3 deletions
diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el
index 8815a72222a..d9c52fa4f0b 100644
--- a/lisp/minibuffer.el
+++ b/lisp/minibuffer.el
@@ -71,7 +71,7 @@ If the value is t the *Completion* buffer is displayed whenever completion
is requested but cannot be done.
If the value is `lazy', the *Completions* buffer is only displayed after
the second failed attempt to complete."
- :type (choice (const nil) (const t) (const lazy))
+ :type '(choice (const nil) (const t) (const lazy))
:group 'minibuffer)
(defun minibuffer--bitset (modified completions exact)
@@ -248,7 +248,7 @@ a repetition of this command will exit."
;; which makes it trivial to find the position, but with fancier
;; completion (plus env-var expansion, ...) `completion' might not
;; look anything like `string' at all.
-
+
(when minibuffer-completing-file-name
;; In order to minimize the problem mentioned above, let's try to
;; reduce the different between `string' and `completion' by
@@ -394,7 +394,7 @@ during running `completion-setup-hook'."
(goto-char (point-max))
(if (null completions)
(insert "There are no possible completions of what you have typed.")
-
+
(insert "Possible completions are:\n")
(minibuffer--insert-strings completions))))
(let ((completion-common-substring common-substring))