> Continuing a lilypond-user discussion on code signing for LilyPond
executables, in hopes of pacifying security software.
On 16/11/2022 7:55 am, Karlin High wrote:
On 11/15/2022 2:30 PM, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
b) whether we would need to buy a
On Tue, 2022-11-15 at 11:44 +0100, Jean Abou Samra wrote:
> Le 15/11/2022 à 10:37, Volodymyr Prokopyuk a écrit :
> > Hi Jean,
> >
> > It worked like a charm! Thank you very much!
> >
> > Maybe it makes sense to put a line in the installation instructions
> > about ../configure
On 11/15/2022 2:30 PM, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
b) whether we would need to buy a certificate for that.
I think the answer is "yes, need to buy certificate."
And even that is no guarantee of executables not getting flagged after
downloads, UNLESS there is
On Mon, 2022-11-14 at 18:31 +0100, Volodymyr Prokopyuk wrote:
> Hi,
>
> It seems that LilyPond v2.23.81 depends on Guile v2.2.
>
> On Linux Arch systems (e. g. Manjaro) Guile v3.0.8 is installed by default.
>
> Currently LilyPond v2.23.81 requires Guile v2.2 as a mandatory dependency,
> which
On Sun, 2022-11-13 at 13:36 -0800, Knute Snortum wrote:
> On Sun, Nov 13, 2022 at 9:38 AM Jonas Hahnfeld via LilyPond user
> discussion wrote:
> >
> > We are happy to announce the release of LilyPond 2.23.81. This is the
> > second release candidate towards the next stable version 2.24.0
> >
Thank you Dan and Jean.
I'll do some experiments in the next few days and I'll update you.
On Tue, Nov 15, 2022 at 2:39 AM Dan Eble wrote:
> On Nov 14, 2022, at 04:43, Paolo Prete wrote:
> >
> > I need to execute the following automated test:
> > given a .ly file, I would like to check if the
Le 15/11/2022 à 15:18, David Kastrup a écrit :
Conversion rules can look at the number of arguments and only revert to
a generic replacement when the number of arguments cannot be determined
(like when the arguments are too complex for the patterns, or
markup-string is not used as a call but as
On Tue, Nov 15, 2022 at 02:49:55PM +0100, Jean Abou Samra wrote:
> Le 15/11/2022 à 14:43, David Kastrup a écrit :
> > If it's "mundane", why would the conversion result in a complex
> > replacement?
>
> Have you looked at the replacement?
>
> It is
>
> (lambda* (m #:optional headers)
> (if
Jean Abou Samra writes:
> Le 15/11/2022 à 14:43, David Kastrup a écrit :
>> If it's "mundane", why would the conversion result in a complex
>> replacement?
>
>
>
> Have you looked at the replacement?
>
> It is
>
> (lambda* (m #:optional headers)
> (if headers
> (markup->string m #:props
Le 15/11/2022 à 14:43, David Kastrup a écrit :
If it's "mundane", why would the conversion result in a complex
replacement?
Have you looked at the replacement?
It is
(lambda* (m #:optional headers)
(if headers
(markup->string m #:props (headers-property-alist-chain headers))
Jean Abou Samra writes:
> Le 15/11/2022 à 14:17, David Kastrup a écrit :
>> Alternatively, providing something approaching the previous behavior
>> under a different name, assuming that this functionality has at least
>> some motivation or possibility to continue existing.
>
>
>
> It's not a
Le 15/11/2022 à 14:17, David Kastrup a écrit :
Alternatively, providing something approaching the previous behavior
under a different name, assuming that this functionality has at least
some motivation or possibility to continue existing.
It's not a behavior change, just a mundane calling
Jean Abou Samra writes:
> Le 15/11/2022 à 00:56, Jean Abou Samra a écrit :
>>> Nevertheless the insertion done by convert-ly is not nice, imho. As a
>>> mere user I'd think some bug happened.
>> In that case, NOT_SMART is the way to go (i.e., not changing
> anything but just printing “Not smart
Le 15/11/2022 à 00:56, Jean Abou Samra a écrit :
Nevertheless the insertion done by convert-ly is not nice, imho. As a
mere user I'd think some bug happened.
In that case, NOT_SMART is the way to go (i.e., not changing anything but just
printing “Not smart enough to convert…”).
Le 15/11/2022 à 10:37, Volodymyr Prokopyuk a écrit :
Hi Jean,
It worked like a charm! Thank you very much!
Maybe it makes sense to put a line in the installation instructions
about ../configure GUILE_FLAVOR=guile-3.0 for those who have Guile 3.0
and build the latest LilyPond from source, if
Hi Jean,
It worked like a charm! Thank you very much!
Maybe it makes sense to put a line in the installation instructions
about ../configure
GUILE_FLAVOR=guile-3.0 for those who have Guile 3.0 and build the latest
LilyPond from source, if it is not already there.
Thank you,
Vlad
On Tue, Nov
16 matches
Mail list logo
