[TxMt] Java language grammar problems
Steve Lianoglou
lists at arachnedesign.net
Wed Mar 29 14:57:39 UTC 2006
Hi folks,
Don't know what happened to my original email, but it seems it got
gobbled up before it even reached the mailing list, so here goes again:
I'm not sure if this is a bug in TM or the java grammar since upon
reviewing the Java Lang definition itself, it seemed to be correct in
the "hey-that-looks-right" sense .. not the "oh-yeah-I-know-what-I'm-
talking-about-and-that's-definitely-right" sense.
I just pulled the latest (everything) from svn. I didn't realize if
the Java.tmbundle was updated, but there are some things going on
which look a bit buggy.
FIRST:
When the cursor is immediately outside of a block comment, the scope
still shows "comment.documentation.java" or "comment.block.java" when
I don't think it should be (imagine the ^ character to be the cursor):
Example:
/* some comment here */^
-- or --
/**
* My method does this
*/^
the scope on the outside of the closed comment is being recognized as
comment.block.java and comment.documentation.java respectively when
really I'm out of the comment blocks.
SECOND:
All the code after an abstract method is scoped to
meta.definition.method.java, like for Example:
public abstract void doSomething();
// all code in the file below this is scoped to the
meta.definition.method.java
if I add a {} at the end of the abstract method signature the scope
gets fixed -- but, y'know ... then the compiler complains :-)
Thanks,
-steve
More information about the textmate
mailing list