Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support grammar changes in Lilypond 2.18 #55

Closed
GoogleCodeExporter opened this issue Apr 14, 2015 · 4 comments
Closed

Support grammar changes in Lilypond 2.18 #55

GoogleCodeExporter opened this issue Apr 14, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

There might be some breaking changes in 2.18. Please investigate and adapt to 
them.

Original issue reported on code.google.com by harmathdenes on 2 Jan 2014 at 11:45

@GoogleCodeExporter
Copy link
Author

One important behavior change is that column numbers in error messages are now 
1-based.

Original comment by harmathdenes on 27 Apr 2014 at 10:06

@GoogleCodeExporter
Copy link
Author

Fixed comment 1 in rf5b7beb.

Original comment by harmathdenes on 27 Apr 2014 at 10:06

@GoogleCodeExporter
Copy link
Author

I just updated to lilypond 2.18.2 and now \upbow was marked as an error in the 
editor and was not suggested by code completion. The reason seems to be the 
following:

script-init.ly contains the following definition which seems not to be parsed 
successfully so that all following definitions (including the one for upbow) 
are not recognized any longer. After moving the problematic definition to the 
end of the file, upbow and the others worked. So here the problematic one:

thumb = \finger \markup \scale #(cons (magstep 5) (magstep 5))
                        \musicglyph #"scripts.thumb"

Anyway, thanks for this extremely cool application to the Xtext framework!!

Original comment by nit...@itemis.de on 11 Mar 2015 at 9:06

@thSoft
Copy link
Owner

thSoft commented Jun 12, 2015

#55 (comment) refers to #58.

@thSoft thSoft closed this as completed Jun 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants