From c92197a243cd77696ea2fedf4361d800ddb59d8c Mon Sep 17 00:00:00 2001 From: Taylor R Campbell Date: Tue, 9 Jul 2013 20:57:28 +0000 Subject: Tweak comment about barfage error. --- paredit.el | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'paredit.el') diff --git a/paredit.el b/paredit.el index 8e52995..e54b1f3 100644 --- a/paredit.el +++ b/paredit.el @@ -2333,8 +2333,8 @@ Automatically reindent the newly barfed S-expression with respect to (backward-sexp)))) (paredit-skip-whitespace nil) ; Skip leading whitespace. (cond ((bobp) - ;++ This will have deleted the close. But there is no - ;++ open. Is that OK? + ;++ We'll have deleted the close, but there's no open. + ;++ Is that OK? (error "Barfing all subexpressions with no open-paren?")) ((paredit-in-comment-p) ; Don't put the close-paren in (newline))) ; a comment. @@ -2473,6 +2473,8 @@ Automatically reindent the barfed S-expression and the form from which (while (progn (paredit-skip-whitespace t) (eq (char-after) ?\; )) (forward-line 1)) (if (eobp) + ;++ We'll have deleted the close, but there's no open. + ;++ Is that OK? (error "Barfing all subexpressions with no close-paren?")) ;** Don't use `insert' here. Consider, e.g., barfing from ;** (foo|) -- cgit v1.2.1