OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Am 25.07.2015 um 18:12 schrieb Víctor: On a separate subject, I'd like to recommend you to use lyluatex instead of Lilypond-book. I've found it to be a cleaner way to work as it is a LuaLaTeX package (developed by the Gregorio team!) and not an engine. I wan

Re: OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Maybe you should write your question in the GitHub page, or in the gregorio project mail list, where its developer will surely read it. He is quite a supportive person, and clearly the most qualified to help you. Víctor. El 26/07/15 a las 05:33, Marc Hohl escribió: Am 25.07.2015 um 18:12 schr

Re: OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Am 27.07.2015 um 06:42 schrieb Víctor: Maybe you should write your question in the GitHub page, or in the gregorio project mail list, where its developer will surely read it. Thanks for your answer! I don't have a GitHub account and do not want to get one just for this question. The same holds

Re: OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Am Sonntag, 26. Juli 2015 12:33 CEST, Marc Hohl schrieb: > Am 25.07.2015 um 18:12 schrieb Víctor: > > On a separate subject, I'd like to recommend you to use lyluatex > > instead of Lilypond-book. I've > > found it to be a cleaner way to work as it is a Lu

Re: OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Am 27.07.2015 um 12:06 schrieb Ralf Mattes: Am Sonntag, 26. Juli 2015 12:33 CEST, Marc Hohl schrieb: Am 25.07.2015 um 18:12 schrieb Víctor: On a separate subject, I'd like to recommend you to use lyluatex instead of Lilypond-book. I've found it to be a cl

Re: OT: Getting lyluatex to work [was: Re: Lilypond and LaTeX - margins]

Pressed send by accident before I was finished. > On Jul 27, 2015, at 11:06 AM, Ralf Mattes wrote: > > > Am Sonntag, 26. Juli 2015 12:33 CEST, Marc Hohl schrieb: > > Not a TeXpert (any more), but from my quick tests - nothing. > I got the same error as you. I "fixed" this bug by adding >