Il giorno dom 7 giu 2015 alle 19:57, Paul Morris
ha scritto:
Keith noted that:
"Looking at the first few lines of update-with-convert-ly, it looks
like it expects you to have defined the build directory as BUILD_DIR
where most other scripts expect LILYPOND_BUILD_DIR.”
A workaround is to run:
ex
Il giorno ven 10 lug 2015 alle 13:56, Ralph Palmer
ha scritto:
What is the current status of the move away from Google Code? Do I
have to
learn a new system for reviewing emails and submitting issues? If so,
I
would like to get started as soon as possible.
Hi Ralph
I'm deploying Allura for
Il giorno ven 10 lug 2015 alle 13:49, Ralph Palmer
ha scritto:
Greetings, Michael, documentation team, and LilyPonders -
Thanks for the email, Michael. I'm not sure if the bug list is the
correct
place to submit this, but I do not know of any list specific to
documentation. This has been subm
Greetings -
What is the current status of the move away from Google Code? Do I have to
learn a new system for reviewing emails and submitting issues? If so, I
would like to get started as soon as possible.
Once again : I'm amazed by and grateful for such a wonderful piece of
software!
Ralph
On Thu, Jul 9, 2015 at 3:03 AM, Michael Gerdau wrote:
> Hi Lilypond documentation team,
>
> in the german version of the Notationsreferenz, Headline 2.9.3
> reads "2.9.3 Mesurale Musik setzen" and it should be
> "2.9.3 Mensurale Musik setzen" (an "n" is missing in Mensurale)
>
> The URL is
>
> ht
>
> >>> %% This tie is nearly invisible before the line break.
> >>> \score {{ r2 f'8 f' f' f'~ \break | f'2 r }}
> >>
> >> I believe that this is issue 14?
> >> https://code.google.com/p/lilypond/issues/detail?id=14
> >
> > Not exactly. My complaint is not that the tie is too short, but that it
>
