Re: Bug with `scan-sexps' / syntax tables in XEmacs-21.4.2
Matt, thanks for the patch. You need to send the patch to
xemacs-patches.
I built 21.5 from the latest CVS sources, and I still see this
behavior, which I had thought was the same as the other problems:
1. Start up xemacs-21.5 -vanilla
2. In the *scratch* buffer, place the cursor after the first closing
parenthesis (at the end of the line which says "while hitting the X
key.)"
3. M-x backward-sexp yields the following error:
Signaling: (syntax-error "Unbalanced parentheses")
scan-sexps(317 -1)
forward-sexp(-1)
backward-sexp(1)
call-interactively(backward-sexp)
command-execute(backward-sexp t)
execute-extended-command(nil)
call-interactively(execute-extended-command)
Sorry I did not report this problem sooner.
Thanks,
vin
Matt Tucker <tuck(a)whistlingfish.net> writes:
-- Vin Shelton <acs(a)xemacs.org> spake thusly:
> Andy Piper <andyp(a)bea.com> writes:
>> I'm sure its a bug. The syntax table stuff seemed to introduce some
>> nasties like this and I wish we could get the fixed (or back out the
>> syntax table stuff). cc-mode is too important.
>
> Agreed. Matt, are you having a chance to look into these failures?
> What's your ETA on a fix?
>
> This has to be fixed before XEmacs 21.4 gets declared stable.
Okay, I've got a fix for this which I've applied to the trunk (21.5).
Since I haven't committed anything since the tree was moved around and
since I'm pretty sure this needs to go in 21.4 as well, I was wondering
what else I should do with the patch. I'd be happy to apply it to the
appropiate branch or let someone else do it; just wasn't sure what the
procedure currently is.
I'll browse back through xemacs-beta to see if there are any other
nasties that need to be fixed that this probably won't address,
although I probably won't have time to fix anything else until next
week.
--
In a minute there is time
For decisions and revisions which a minute will reverse. T.S. Eliot
[URL: http://www.cs.amherst.edu/~ccm/prufrock.html]