lisp error opening .js file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open <a specific .js file>
2.
3.

What is the expected output? What do you see instead?

Expected a nicely highlighted file, got a backtrace.

What version of the product are you using? On what operating system?

The version is:

;;; This file was auto-generated on Sun Apr 06 23:28:49 2008 from files:

On emacs 22.2.1 on Centos 5.1.

Please provide any additional information below.

Attached error trace.

Original issue reported on code.google.com by mpsteven...@gmail.com on 8 Apr 2008 at 12:35

Attachments:

• error.txt

[GoogleCodeExporter]

Sorry, this is a dupe of issue 23, created due to google code telling me the 
submit
had failed and I needed to retry, when it had actually succeeded.

Original comment by mpsteven...@gmail.com on 8 Apr 2008 at 12:37

[GoogleCodeExporter]

I'm afraid you'll have to provide me with a snippet of JavaScript that produces 
the
error, or I won't be able to reproduce it.  Not clear from the stack trace how 
the
problem is triggered.

Original comment by steve.ye...@gmail.com on 14 Apr 2008 at 10:18

[GoogleCodeExporter]

This snippet triggers the problem for me.

Original comment by mpsteven...@gmail.com on 14 Apr 2008 at 11:02

Attachments:

• test8.js

[GoogleCodeExporter]

Thanks.  The error will be fixed in the next release.

Note that your JavaScript in this snippet is invalid since it contains an 
unescaped
newline in a string, resulting in throwing lots of downstream parse errors.  But
you're right - the mode shouldn't just puke when it encounters a scan error 
like this.

Original comment by steve.ye...@gmail.com on 15 Apr 2008 at 10:50

• Changed state: Started
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by steve.ye...@gmail.com on 16 Apr 2008 at 9:43

• Changed state: Pending

[GoogleCodeExporter]

Original comment by steve.ye...@gmail.com on 19 Apr 2008 at 10:53

• Changed state: Fixed