Yes, that's an architectural problem of jEdit. But this is not a problem for most lilypond files :-)
But I had no other issues with jEdit other than performance, > especially with large files (over 2 MB). For work, I sometimes have to look > at web logs, and those are about 100 MB long text files, I tried opening one > up with jEdit and it simply locked itself up, whereas in other editors I > could get to page 1 immediately in under a second. I think jEdit was > actualy trying to read/parse the entire file, when my scrollbar was really > just on page 1, but thats just a programming problem with jEdit I guess > (that it should try to bring the whole 100MB file into memory at once). > > > > > -- > View this message in context: > http://www.nabble.com/lilypond-and-editors-tf2734613.html#a7864890 > Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. > > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
