aboutsummaryrefslogtreecommitdiffstats
path: root/lisp/complete.el
diff options
context:
space:
mode:
Diffstat (limited to 'lisp/complete.el')
-rw-r--r--lisp/complete.el6
1 files changed, 3 insertions, 3 deletions
diff --git a/lisp/complete.el b/lisp/complete.el
index 058bcd7e8ad..95e116f7536 100644
--- a/lisp/complete.el
+++ b/lisp/complete.el
@@ -933,7 +933,7 @@ or properties are considered."
933 ;; completions of "(ne", which is presumably not what one wants. 933 ;; completions of "(ne", which is presumably not what one wants.
934 ;; 934 ;;
935 ;; This is arguably (at least, it seems to be the existing intended 935 ;; This is arguably (at least, it seems to be the existing intended
936 ;; behaviour) what one _does_ want if point has been explicitly 936 ;; behavior) what one _does_ want if point has been explicitly
937 ;; positioned on the hyphen. Note that if PC-do-completion (qv) binds 937 ;; positioned on the hyphen. Note that if PC-do-completion (qv) binds
938 ;; completion-base-size to nil, then completion does not replace the 938 ;; completion-base-size to nil, then completion does not replace the
939 ;; correct amount of text in such cases. 939 ;; correct amount of text in such cases.
@@ -945,12 +945,12 @@ or properties are considered."
945 ;; the minibuffer. The same is not true for lisp symbols. 945 ;; the minibuffer. The same is not true for lisp symbols.
946 ;; 946 ;;
947 ;; [1] An alternate fix would be to not move point to the hyphen 947 ;; [1] An alternate fix would be to not move point to the hyphen
948 ;; in such cases, but that would make the behaviour different from 948 ;; in such cases, but that would make the behavior different from
949 ;; that for filenames. It seems PC moves point to the site of the 949 ;; that for filenames. It seems PC moves point to the site of the
950 ;; first difference between the possible completions. 950 ;; first difference between the possible completions.
951 ;; 951 ;;
952 ;; Alternatively alternatively, maybe end should be computed in 952 ;; Alternatively alternatively, maybe end should be computed in
953 ;; the same way as beg. That would change the behaviour though. 953 ;; the same way as beg. That would change the behavior though.
954 (if (equal last-command 'PC-lisp-complete-symbol) 954 (if (equal last-command 'PC-lisp-complete-symbol)
955 (PC-do-completion nil beg PC-lisp-complete-end t) 955 (PC-do-completion nil beg PC-lisp-complete-end t)
956 (if PC-lisp-complete-end 956 (if PC-lisp-complete-end