GNU bug report logs -
#7921
23.2.91; js-mode font lock problem with comments
Previous Next
Reported by: Evan Owens <eaowens <at> gmail.com>
Date: Wed, 26 Jan 2011 16:03:02 UTC
Severity: minor
Found in version 23.2.91
Done: Simen Heggestøyl <simenheg <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #26 received at 7921 <at> debbugs.gnu.org (full text, mbox):
2011/1/27 Stefan Monnier <monnier <at> iro.umontreal.ca>:
>>>> path=/";/ # Everything following and including the last / is string face
>>>> path="; # Everything is fine
>>>> path=//"; # Everything is fine
>>>
>>> I've put the above three lines in ~/tmp/foo.js and opened it with
>>> Debian's emacs23 and I don't think I see the problems you describe in
>>> the comments. OTOH I see other problems of highlighting but they're
>>> largely due to the code itself being meaningless, AFAIK (# is not
>>> a comment marker in javascript, is it?).
>>>
>
>> I'm sorry, I should have been more clear. The # signs are
>> meta-comments, please leave them out when trying to reproduce the
>> problem.
>
> In my tests, the ";\npath=//" is treated as a string. This sounds right
> to me, but not being a js-programmer, your example makes me doubt.
> IOW, using the latest code in the emacs-23, are there still some issues
> with js-mode's font-locking?
>
Assuming that you mean "; npath=//", it is indeed correctly fontified
as a string.
I notice now that I referred to the three JavaScript examples as
"issues" -- they are not issues.
Only the last two examples are valid JavaScript. The first example,
even though _invalid_ JavaScript, might give us a hint about what the
problem is. That is the only reason why I included it.
--
Deniz Dogan
This bug report was last modified 9 years and 165 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.