On Dec 4, 2014, at 09:58 , Masamichi HOSODA wrote:
>
>> Also, the mention of optimization reminds me of one of the horrors of
>> floating point types: a value in a register can quietly be changed when it
>> is written to memory. Take a look at some of the “myths” in section 1 of
>> https://ha
> What defines the distance between a time signature and the next note
> *with an accidental* (in addition to the TimeSignatures
> `extra-spacing-width')? I would expect that the `first-note' (or
> `next-note', if set) element of a TimeSignature's `space-alist'
> handles this case also, but this
>> There is this at the end of skyline.cc:
>>
>> // Should add during ver2.19 (to avoid an endless loop
>> // when merging identical skylines with a vertical segment)
>> // if (end >= s2->front().end_) s2->pop_front();
>
> I meant at the end of internal_merge_skyline() in skyline.
>>> I changed mingw.org's mingw-runtime to mingw-64 (32-bit).
>>> Then an error didn't occur and correct test.pdf was generated.
>>>
>>> https://github.com/trueroad/gub/tree/binutils-2.24
>>>
>>> I may pull request if you request it.
>>>
>>> Further, even if the r
On 02/12/14 16:00, Urs Liska wrote:
Am 02.12.2014 16:58, schrieb Paul Morris:
Urs Liska wrote
I just stumbled over
http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and
http://lilypond.org/website/gsoc-2012.html
I still think it would be best to convert it into a generic
