Bad interaction with paredit-kill

[Gwen Weinholt]

Using the latest paredit-beta and your scheme-mode, there is a problem with paredit-kill in strings. To reproduce this I ran emacs -q and require'd paredit and scheme. Then I switched to a new buffer and enabled scheme-mode and then paredit-mode. Type "foo" and put the cursor on the 'f' and then type C-k. There is an error:
forward-sexp: Scan error: "Unbalanced parentheses", 1, 1

This problem does not occur with e.g. lisp-mode + paredit-mode. I hope this is enough for you to reproduce it (since paredit-beta.el says it's hard to reproduce problems with paredit-kill).

http://mumble.net/~campbell/emacs/paredit-beta.el of 2008-12-15.
GNU Emacs 23.0.60.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.12.11) of 2009-01-03 on industria
And scheme-mode rev 11.

[Gwen Weinholt (weinholt)]

I found another bad interaction with paredit (maybe these are bugs in paredit?). paredit-forward-slurp-sexp doesn't work properly, because of another "unbalanced parenthesis" error. To reproduce you can make the buffer look like this:

() foo

and then position the cursor on ')' and type C-). The closing parenthesis disappears and there is an error message:
up-list: Scan error: "Unbalanced parentheses", 6, 6

[Gwen Weinholt (weinholt)]

A possible clue: open up a new buffer and type (if foo RET. When typing RET there is an error:
forward-sexp: Scan error: "Unbalanced parentheses", 1, 9
and this is without paredit-mode even loaded.

[Derick Eddington (derick-eddington)]

Confirmed with Paredit versions 20 and 21.

[Derick Eddington (derick-eddington)]

All fixed in revision 13. All three bugs were because scheme-beginning-of-top-level-form was not fully working like Emacs' default beginning-of-defun.