On 18/07/2014 4:56 PM, Julien Rioux wrote:
On 18/07/2014 4:21 PM, Br. Samuel Springuel wrote:
I'm running LilyPond 2.18.2 on a Mac OS 10.8.5 and reported the same
error back in June:
http://lists.gnu.org/archive/html/lilypond-user/2014-06/msg00610.html
The problem (at least for me) seems to oc
Time to get back to work! :)
2014-07-28 23:33 GMT+02:00 Trevor Daniels :
> If your code changes necessitate a change to the documentation and you
> haven't done this yourself, please add an issue to the tracker explaining
> what changes and/or additions need to be made to the documentation at
> th
Janek Warchoł writes:
> PS interestingly, while whatever is \accepted by StaffGroups seems to
> be \accepted by ChoirStaffs, PianoStaffs and GrandStaffs won't accept
> new contexts unless explicitly told.
It's more like ChoirStaffs accept a StaffGroup (which is then implicitly
created and accept
Am 01.08.2014 16:19, schrieb Jos Leussink:
I'm not top posting.
wellcome test file of version 2.18 mentions:
\version "2.16.0"
You’ll find many files in the lily distribution which carry an older
version statement, since there was no update (and needn’t have been).
This is surprising at first,
"Jos Leussink" wrote in message
news:loom.20140801t161456-...@post.gmane.org...
I'm not top posting.
wellcome test file of version 2.18 mentions:
\version "2.16.0"
Thanks. It's an issue we spotted a couple of months ago, and development
versions since 2.19.6 have used the correct version nu
> I'm not top posting.
wellcome test file of version 2.18 mentions:
\version "2.16.0"
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
