Re: two pipelines for a single merge

2022-11-18 Thread Jean Abou Samra
> Le 19 nov. 2022 à 08:42, Werner LEMBERG a écrit : > >  > Looking into > > https://gitlab.com/lilypond/lilypond/-/pipelines > > I see that for every merge I do, two pipelines are executed. > Apparently, this doesn't happen for Jean. What am I doing wrong? Nothing. There is one

two pipelines for a single merge

2022-11-18 Thread Werner LEMBERG
Looking into https://gitlab.com/lilypond/lilypond/-/pipelines I see that for every merge I do, two pipelines are executed. Apparently, this doesn't happen for Jean. What am I doing wrong? Note that I simply press the 'Rebase' button followed by 'Merge if rebase succeeds'. Werner

Re: strut problem, Re: strut problem, Re: strut problem, Re: strut problem

2022-11-18 Thread Jean Abou Samra
 > Le 19 nov. 2022 à 08:04, Werner LEMBERG a écrit : >  >> A stencil has an X extent, a Y extent and a stencil expression >> (Scheme list). That's all. >> Think of it in another way. If LilyPond gave non-empty skylines to >> stencils with empty extents, a grob with its stencil set to >>

Re: strut problem,Re: strut problem,Re: strut problem,Re: strut problem

2022-11-18 Thread Werner LEMBERG
> A stencil has an X extent, a Y extent and a stencil expression > (Scheme list). That's all. > > Think of it in another way. If LilyPond gave non-empty skylines to > stencils with empty extents, a grob with its stencil set to > #empty-stencil would stop taking no space. Instead, it would take >

PATCHES - Countdown to November 21

2022-11-18 Thread Colin Campbell
Here is the current countdown report. The next countdown will begin on November 21st. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1732 convert-ly: Print "not smart" message for markup->string - Jean

Re: BDWGC fix in 2.24?

2022-11-18 Thread Jean Abou Samra
Le 18/11/2022 à 16:17, Kevin Barry a écrit : On Fri, Nov 18, 2022 at 11:06:45AM +0100, Jean Abou Samra wrote: Hi, What should we do? Do we accept releasing 2.24 from the release-8_2 branch in BDWGC even though it is not released? Do we keep the current workaround, which still gives some

Re: strut problem,Re: strut problem

2022-11-18 Thread Jean Abou Samra
Le 18/11/2022 à 23:16, Werner LEMBERG a écrit : Put yourself in the shoes of LilyPond trying to compute the skylines of this stencil: (ly:make-stencil "" empty-interval '(-0.3 . 0.7)) According to you, the skyline should be a zero-width spike. At which horizontal coordinate is this spike? Any

Re: strut problem,Re: strut problem

2022-11-18 Thread Werner LEMBERG
> Put yourself in the shoes of LilyPond trying to compute the skylines > of this stencil: > > (ly:make-stencil "" empty-interval '(-0.3 . 0.7)) > > According to you, the skyline should be a zero-width spike. At > which horizontal coordinate is this spike? Any value would be > legitimate.

Re: strut problem,Re: strut problem,Re: strut problem,Re: strut problem

2022-11-18 Thread Werner LEMBERG
> You did see the code I posted that would do what you asked for? Sorry, no, I missed it. Thanks! Werner

Re: BDWGC fix in 2.24?

2022-11-18 Thread Kevin Barry
On Fri, Nov 18, 2022 at 11:06:45AM +0100, Jean Abou Samra wrote: > Hi, > > What should we do? Do we accept releasing 2.24 from > the release-8_2 branch in BDWGC even though it is not > released? Do we keep the current workaround, which still > gives some crashes? Do we replace our workaround >

Re: BDWGC fix in 2.24?

2022-11-18 Thread Karlin High
On 11/18/2022 4:06 AM, Jean Abou Samra wrote: Do we keep the current workaround, which still gives some crashes? In that case, possibly releasing with a "known issue" note, and explaining how Windows users could use Windows Subsystem for Linux if they have very large scores approaching

Re: strut problem,Re: strut problem,Re: strut problem,Re: strut problem

2022-11-18 Thread David Kastrup
Werner LEMBERG writes: > Why is the vertical extent of the strut ignored? Because side positioning is primarily based on (vertical) skylines, not extents. >>> >>> Thanks. What is the reasoning behind this? For me, this behaviour >>> is unexpected. >> >> By the way, this is

Re: strut problem

2022-11-18 Thread Jean Abou Samra
Le 18/11/2022 à 12:34, Werner LEMBERG a écrit : It is completely unclear to me how you would take non-printing stencils with empty extents into skylines. How should the resulting skylines look like? If the X extent is empty-interval, why should the vertical skyline take this stencil into

Re: strut problem,Re: strut problem

2022-11-18 Thread Werner LEMBERG
>> What I suggest is that zero-width/zero-height objects >> *are* taken in account for computing the skylines. > > What makes your (redefined) \strut not taken into account [...] is > caused by the "" stencil expression, which LilyPond never gives > skylines to Ah, thanks. > It is completely

Re: strut problem

2022-11-18 Thread Jean Abou Samra
Le 18/11/2022 à 12:05, Werner LEMBERG a écrit : The latter. What I suggest is that zero-width/zero-height objects *are* taken in account for computing the skylines. What makes your (redefined) \strut not taken into account into skylines is not just its empty X extent. You can see that it is

Re: strut problem

2022-11-18 Thread Werner LEMBERG
>> However, the longer I think about struts – even `\vspace` is >> nothing else than a vertical strut! – the more I believe that there >> is a conceptual problem in LilyPond: There is a 'typesetting mode' >> where vertical struts have an effect (like the problem originally >> reported in

Re: strut problem

2022-11-18 Thread Jean Abou Samra
Le 18/11/2022 à 05:46, Werner LEMBERG a écrit : You are correct with your LaTeX observation. However, the longer I think about struts – even `\vspace` is nothing else than a vertical strut! – the more I believe that there is a conceptual problem in LilyPond: There is a 'typesetting mode' where

BDWGC fix in 2.24?

2022-11-18 Thread Jean Abou Samra
Hi, As illustrated by a recent message on lilypond-user, the GC issue on Windows is still there for very large scores in 2.23.81. In https://github.com/ivmai/bdwgc/issues/454#issuecomment-1313127991 the BDWGC maintainer said the release of his fix would probably happen in January, which is