2014-07-17 17:10 GMT+02:00 Urs Liska :
> For lilypond-devel: We had talked about this option for the LilyPond
> manuals. Having had my first experience I think we should give that another
> thought. Have a look at the commit
> https://github.com/openlilylib/openlilylib/commit/
> 568c3ef1c70dfa5619
Hi,
because of that unwanted merge while the patch for issue 3992 was
pushed, i'm not sure what to do with my own patch for issue 4008.
Should I wait before I push myself?
Cheers,
Harm
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://l
Thomas Morley writes:
> Hi,
>
> because of that unwanted merge while the patch for issue 3992 was
> pushed, i'm not sure what to do with my own patch for issue 4008.
>
> Should I wait before I push myself?
If the question is whether we will going to change anything in the
repository: no. Any cl
So, Urs and I have been discussing how we might proceed to make alternate
music fonts more publicly available and I thought I'd bring the discussion
here since there are some decisions to be made regarding how users would
experience the change.
- Question 1: *Should the new syntax be something lik
On 19. Juli 2014 16:48:55 MESZ, tisimst wrote:
>So, Urs and I have been discussing how we might proceed to make
>alternate
>music fonts more publicly available and I thought I'd bring the
>discussion
>here since there are some decisions to be made regarding how users
>would
>experience the chang
Urs Liska writes:
> On 19. Juli 2014 16:48:55 MESZ, tisimst wrote:
>>So, Urs and I have been discussing how we might proceed to make
>>alternate
>>music fonts more publicly available and I thought I'd bring the
>>discussion
>>here since there are some decisions to be made regarding how users
>>w