On 4/7/16 4:54 PM, "Urs Liska" wrote:
>
>So it is really strange, I'm completely at a loss to find out where to
>start looking further ...
Have you worked your way through Phil's notes at
http://lilypond.org/doc/v2.19/Documentation/contributor/the-function-of-mak
e-doc
Carl
__
Am 07.04.2016 um 11:11 schrieb Carl Sorensen:
> On 4/7/16 12:11 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Urs Liska" behalf of
> u...@openlilylib.org> wrote:
>
>> However, when *deleting* the .py and .pyc files an error was triggered,
>> when lilypond-book tries to i
Am 01.04.2016 um 23:59 schrieb Simon Albrecht:
Hello,
using Completion_heads_engraver and Completion_rests_engraver means a
lot of typing, and yet it is a pretty stereotypical action. So I thought
about introducing a context modification identifier (like
\RemoveEmptyStaves) for this task. Do you
Am 07.04.2016 um 12:11 schrieb David Kastrup:
> David Kastrup writes:
>
>> Carl Sorensen writes:
>>
>>> What about if you delete python/out and redo make doc?
>>>
>>> Just wondering if there's something wrong with the build script that
>>> python/out isn't properly recreated when python/*.py ch
David Kastrup writes:
> Carl Sorensen writes:
>
>> What about if you delete python/out and redo make doc?
>>
>> Just wondering if there's something wrong with the build script that
>> python/out isn't properly recreated when python/*.py changes. In my
>> setup, python/*.py is not executable, bu
Carl Sorensen writes:
> What about if you delete python/out and redo make doc?
>
> Just wondering if there's something wrong with the build script that
> python/out isn't properly recreated when python/*.py changes. In my
> setup, python/*.py is not executable, but python/out/*.py is. So make i
On 4/7/16 12:11 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
behalf of Urs Liska" wrote:
>
>
>However, when *deleting* the .py and .pyc files an error was triggered,
>when lilypond-book tries to import book_html.
>
>Looking further into it I realized:
>- book_base keeps an array with