diff options
| author | Taylor R Campbell <campbell@mumble.net> | 2013-07-09 20:57:28 +0000 | 
|---|---|---|
| committer | Taylor R Campbell <campbell@mumble.net> | 2013-07-09 20:57:28 +0000 | 
| commit | c92197a243cd77696ea2fedf4361d800ddb59d8c (patch) | |
| tree | 67dbd3d5de80524d7545e1376b7dd66dc8b12087 | |
| parent | e0af01a1d55d428c074c8d62b60b99aad17dbbb3 (diff) | |
Tweak comment about barfage error.
| -rw-r--r-- | paredit.el | 6 | 
1 files changed, 4 insertions, 2 deletions
| @@ -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|) | 
