summaryrefslogtreecommitdiff
path: root/lisp/pcomplete.el
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2022-12-04 14:42:07 +0200
committerEli Zaretskii <eliz@gnu.org>2022-12-04 14:42:07 +0200
commit3768b1007775d58c3cadb1b3198209e71afefc52 (patch)
treea458f6bc275eef8afe3de663c39e50277fe4f8cc /lisp/pcomplete.el
parent84214578f5a2ff0d45312d9385442583f6877fb5 (diff)
downloademacs-3768b1007775d58c3cadb1b3198209e71afefc52.tar.gz
emacs-3768b1007775d58c3cadb1b3198209e71afefc52.tar.bz2
emacs-3768b1007775d58c3cadb1b3198209e71afefc52.zip
; * lisp/pcomplete.el (pcomplete-allow-modifications): Fix a typo.
Diffstat (limited to 'lisp/pcomplete.el')
-rw-r--r--lisp/pcomplete.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/pcomplete.el b/lisp/pcomplete.el
index ef286b70fe0..8be026b5a82 100644
--- a/lisp/pcomplete.el
+++ b/lisp/pcomplete.el
@@ -193,7 +193,7 @@ and how is entirely up to the behavior of the
"If non-nil, allow effects in `pcomplete-parse-arguments-function'.
For the `pcomplete' command, it was common for functions in
`pcomplete-parse-arguments-function' to make modifications to the
-buffer, like expanding variables are such.
+buffer, like expanding variables and such.
For `completion-at-point-functions', this is not an option any more, so
this variable is used to tell `pcomplete-parse-arguments-function'
whether it can do the modifications like it used to, or whether