summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTaylor R Campbell <campbell@mumble.net>2011-03-20 17:18:05 +0000
committerTaylor R Campbell <campbell@mumble.net>2011-03-20 17:18:05 +0000
commit3f6b2946e4f963c596c8e088764cbd8d80bbf661 (patch)
treee08b77d8092d15510963a14be7926fa54f35f85c
parent73c481aad0af84f01649d8f1616c0d022aca9c42 (diff)
Fix comment in `paredit-forward' on `up-list' vs `forward-char'.
Ignore-this: 87926a2083bf8b1444aa83d80c5346fb Add analogous comment to `paredit-backward'. Thanks, Eitan Postavsky. darcs-hash:20110320171805-00fcc-e0817b0a6f305681267cc804a680e64d9eff1b96
-rw-r--r--paredit.el5
1 files changed, 4 insertions, 1 deletions
diff --git a/paredit.el b/paredit.el
index 2f6a0f1..e00df9d 100644
--- a/paredit.el
+++ b/paredit.el
@@ -1679,7 +1679,8 @@ If there are no more S-expressions in this one before the closing
past the S-expression following the point."
(paredit-handle-sexp-errors
(forward-sexp)
- ;++ Is it necessary to use UP-LIST and not just FORWARD-CHAR?
+ ;; Use `up-list' if outside a string in case there is whitespace
+ ;; between the point and the end of the list.
(if (paredit-in-string-p) (forward-char) (up-list))))
(defun-saving-mark paredit-backward ()
@@ -1689,6 +1690,8 @@ If there are no more S-expressions in this one before the opening
move backward past the S-expression preceding the point."
(paredit-handle-sexp-errors
(backward-sexp)
+ ;; Use `backward-up-list' if outside a string in case there is
+ ;; whitespace between the point and the beginning of the list.
(if (paredit-in-string-p) (backward-char) (backward-up-list))))
;;; Why is this not in lisp.el?