Function `elbow-hairpin` is defined as
(define ((elbowed-hairpin coords mirrored?) grob)
...
(export elbowed-hairpin)
Functions `flared-hairpin` and `constante-hairpin` are defined as
(define-public flared-hairpin
(elbowed-hairpin '((0 . 0) (0.95 . 0.4) (1.0 . 1.0)) #t))
(defi
>> A quick work-around is to use Guile 2.x, as Jean has reported in
>> !808...
>
> Is that actually better? Last time I had contact with Guile-2.x in
> that respect, it replaced the argument lists by generic a b c d .
> That would be different here?
I don't know. I have always used 1.x; I have
Werner LEMBERG writes:
>>> In `notation.pdf`, section 'A.23, Scheme functions', the function
>>> header
>>>
>>> (define-safe-public (check-context-path path #:optional location)
>>>
>>> gets currently translated to
>>>
>>> check-context-path path . lambda*:G59
>
> A quick work-around is to us
>> In `notation.pdf`, section 'A.23, Scheme functions', the function
>> header
>>
>> (define-safe-public (check-context-path path #:optional location)
>>
>> gets currently translated to
>>
>> check-context-path path . lambda*:G59
A quick work-around is to use Guile 2.x, as Jean has reported
Hi everybody,
is there any reason that we still use very ancient versions of ghostscript for
our installers prepared via GUB?
A number of vulnerabilities have been found, and it's easy to find detailed
descriptions of exploits ... see e.g.
https://www.openwall.com/lists/oss-security/2019/01/2
>> I remember faintly that you've mentioned something along this
>> direction [...]
>
> see https://gitlab.com/lilypond/lilypond/-/merge_requests/808
Ah thanks, this was it.
Werner
