It took me a while to notice that the plugin does a syntax check when
you save. This is *really* nice since it saves having to do a lilypond
run and then hunt for the errors by line number. It missed the
following error that I made: I had typed "a(," instead of "a,(". jEdit
found no errors, but lilypond didn't like that.
The jEdit plugin will (in the following months) get an almost real
LilyPond parser, that finds errors like this one. No it has a very
simple block-closed or not closed checking.
Bert
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
