Re: MacOS release help

Hi Carl, > IMO, what we most want is an app bundle that can be easily relocated > anywhere and that provides all of the binaries used by LilyPond. > Frescobaldi can be pointed at that app bundle to run LilyPond. That sounds great to me! > In my opinion, we want to have > a) an installer for

PATCHES - Countdown to October 19

Here is the current countdown report. The next countdown will begin on October 19th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: !1671 Avoid deprecated fgrep

Re: MacOS release help

On Mon, Oct 17, 2022 at 3:49 PM Alex Harker wrote: > This is a continuation of the discussion from lilypond-u...@gnu.org > in a more appropriate place. > > I’m responding to Jean and Jonas together as the two most recent sets of > comments were strongly related. >

MacOS release help

This is a continuation of the discussion from lilypond-u...@gnu.org in a more appropriate place. I’m responding to Jean and Jonas together as the two most recent sets of comments were strongly related. > On 17 Oct 2022, at 20:33, Jean Abou Samra wrote: > > I

Re: Snippet 860 not necessary

Ah, I see. My bad. Am Mo., 17. Okt. 2022 um 21:50 Uhr schrieb Jean Abou Samra < j...@abou-samra.fr>: > Le 17/10/2022 à 21:45, Jean Abou Samra a écrit : > > Le 17/10/2022 à 21:29, Martín Rincón Botero a écrit : > >> Hello, > >> > >> I just discovered that printing a tuplet bracket when on the

Re: weird error engraving two files with 2.23.14

> \column \override #'(font-name . "Arial Bold") { >D A F♯ D A D > } Using `font-name` is 'absolute', that is, it overrides any LilyPond font switching mechanism. This means that `\number` doesn't work. There are two solutions: Either set up a font tree so that you can use standard

Re: weird error engraving two files with 2.23.14

Le 17/10/2022 à 22:13, Federico Bruni a écrit : Sorry, I should have not put that link, as it only works in 2.22 and no longer in 2.23. Here's a minimal example: \version "2.23.14" tuningOpenD = \markup {  \fontsize #-4  \override #'(baseline-skip . 1.5)  \column \override #'(font-name .

Re: weird error engraving two files with 2.23.14

On 2022-10-17 1:13 pm, Federico Bruni wrote: Sorry, I should have not put that link, as it only works in 2.22 and no longer in 2.23. Here's a minimal example: \version "2.23.14" tuningOpenD = \markup { \fontsize #-4 \override #'(baseline-skip . 1.5) \column \override #'(font-name . "Arial

Re: source file ... .scm newer than compiled ... .go file

Il giorno dom 16 ott 2022 alle 21:35:39 +0200, Jean Abou Samra ha scritto: Le 16/10/2022 à 20:41, Federico Bruni a écrit : Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra  ha scritto: Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond development a écrit :

Re: weird error engraving two files with 2.23.14

Il giorno dom 16 ott 2022 alle 21:07:22 +0200, Jean Abou Samra ha scritto: Le 16/10/2022 à 20:54, Federico Bruni a écrit : Il giorno dom 16 ott 2022 alle 12:19:46 +0200, Jean Abou Samra  ha scritto: Le 14/10/2022 à 22:19, Federico Bruni a écrit : I also had to replace # with ♯

Re: Snippet 860 not necessary

Le 17/10/2022 à 21:45, Jean Abou Samra a écrit : Le 17/10/2022 à 21:29, Martín Rincón Botero a écrit : Hello, I just discovered that printing a tuplet bracket when on the note head side had a corresponding workaround in the LSR. This snippet is not necessary anymore since 2.23.14 and should

Re: Snippet 860 not necessary

Le 17/10/2022 à 21:29, Martín Rincón Botero a écrit : Hello, I just discovered that printing a tuplet bracket when on the note head side had a corresponding workaround in the LSR. This snippet is not necessary anymore since 2.23.14 and should be deleted https://lsr.di.unimi.it/LSR/Item?id=860.

Snippet 860 not necessary

Hello, I just discovered that printing a tuplet bracket when on the note head side had a corresponding workaround in the LSR. This snippet is not necessary anymore since 2.23.14 and should be deleted https://lsr.di.unimi.it/LSR/Item?id=860. I think Harm is the one who does that, right? —Martín.

Re: output-attributes on Cairo backend

Le 17/10/2022 à 18:06, Paolo Prete a écrit : Thanks for this information. The issue was created 12 years ago (!) and it received no feedback. Therefore I presume it won't be fixed because there's no interest in fixing it. I would not be so quick. FLOSS projects are developed on a long

Re: output-attributes on Cairo backend

On Mon, Oct 17, 2022 at 6:06 PM Paolo Prete wrote: > > > On Sun, Oct 16, 2022 at 1:52 PM Jean Abou Samra > wrote: > >> >> >> Thanks for reminding me, this is something that I wanted to >> share on this list but I forgot. We have a bit of a problem here, >> because Cairo doesn't support setting

Re: LilyPond 2.23.14

On Mon, 2022-10-17 at 04:29 -0500, Karlin High wrote: > On Sun, Oct 9, 2022 at 3:57 PM Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > please test with your use cases and notify us of any problems. > > I spent a few hours yesterday with LilyPond 2.23.14 and Frescobaldi > 3.2,

Re: output-attributes on Cairo backend

On Sun, Oct 16, 2022 at 1:52 PM Jean Abou Samra wrote: > > > Thanks for reminding me, this is something that I wanted to > share on this list but I forgot. We have a bit of a problem here, > because Cairo doesn't support setting arbitrary attributes in SVG > output right now. This corresponds to

Re: LilyPond 2.23.14

Hi all, > On Sun, Oct 9, 2022 at 3:57 PM Jonas Hahnfeld via Discussions on > LilyPond development wrote: >> please test with your use cases and notify us of any problems. I have been using 2.23.14 very heavily, on a large set of relatively complicated and inter-connected files, in a

Re: LilyPond 2.23.14

On Sun, Oct 9, 2022 at 3:57 PM Jonas Hahnfeld via Discussions on LilyPond development wrote: > please test with your use cases and notify us of any problems. I spent a few hours yesterday with LilyPond 2.23.14 and Frescobaldi 3.2, on Windows 10 21H1. While I am not the most demanding user --