From: Alan Third <alan@idiocy.org>
To: Alexander Haeckel <alexanderhaeckel@lavabit.com>
Cc: 7498@debbugs.gnu.org, alexander.haeckel@web.de
Subject: bug#7498: 23.2; scheme-mode.el doesn't parse racket file correctly
Date: Fri, 12 Aug 2016 20:12:14 +0100 [thread overview]
Message-ID: <m2twepol81.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <matrix.87sjymg2pz.fsf@alex-haeckel.de> (Alexander Haeckel's message of "Sat, 27 Nov 2010 17:18:00 +0100")
Alexander Haeckel <alexanderhaeckel@lavabit.com> writes:
> I describe the problem from 'emacs -Q':
> scheme-mode.el isn't able to correctly parse the file:
> racket-5.0.2/collects/drracket/tool-lib.rkt
> When I open the file, go to position (79,0)
> and execute `forward-sexp' I get
> Scan error: "Unbalanced parentheses", 2852, 65105
>
> The expected behaviour is for the point to be moved at the end
> of the file behind the last closing parenthesis to position (1663,85).
> When I move the point at the end of the file behind the last closing
> parenthesis and do `backward-sexp' the point is moved to line
> the point is moved to position (152,19) instead to (79,0), where
> the next character is an opening curly brace.
There are lines of the form:
@item{@racket[error-print-width] is set to 250;}
that appear to break things, because scheme-mode sees that closing curly
bracket as a comment. This syntax looks like it’s Racket specific.
My elisp skills aren’t good enough to tell if this is fixable.
--
Alan Third
next prev parent reply other threads:[~2016-08-12 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 16:18 bug#7498: 23.2; scheme-mode.el doesn't parse racket file correctly Alexander Haeckel
2016-08-12 19:12 ` Alan Third [this message]
2016-08-12 20:37 ` Clément Pit--Claudel
2016-09-10 21:37 ` Alan Third
2020-11-19 4:46 ` Stefan Kangas
2020-11-19 5:25 ` Jean Louis
2021-10-21 19:44 ` Stefan Kangas
2021-10-21 20:18 ` Philip Kaludercic
2021-10-21 20:45 ` Stefan Kangas
2021-10-21 21:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-21 22:05 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2twepol81.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=7498@debbugs.gnu.org \
--cc=alexander.haeckel@web.de \
--cc=alexanderhaeckel@lavabit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).