Re: Include all files in a folder

On Sun, Jan 21, 2024 at 7:00 PM Aaron Hill wrote: > \includePattern has a \version statement with 2.24.0, so it would appear > to still be relevant. > Sure enough! I had experimented with that a little but had already counted it as yet another defeat at getting OpenLilyLib working on Windows. W

Re: Include all files in a folder

On 2024-01-21 4:43 pm, Karlin High wrote: The question was answered in 2016: What would be the current version of the answer? \includePattern [1] has a \version statement with 2.24.0, so it would appear to still be rele

Include all files in a folder

The question was answered in 2016: What would be the current version of the answer? -- Karlin High Missouri, USA

Re: Output PDF to stdout

Hello Vlad, You will not avoid intermediate files in any case, as Lilypond with gs output will generate ps code, which is then turned into a pdf. If you want to pipe PDFs for convenience you might create a wrapper say plilypond in the search path doing something like this: #!/bin/bash t=$(mkt

Repeatmark replacement in petrucci style broken?

Dear all, following code used to work fine with LilyPond 2.22.x (Debian 11) after upgrade to LilyPond 2.24.1 (Debian 12) somehow the repeatmark replacement fails. As far as I read it in the documentation the \bar command should still work to do that? I tried adding the \bar also to the \supe

Re: Drum notation and style

Yes, it very likely is not formally correct. As pointed out in the original post: > I'm not sure if the bottom version is formally correct, but I would like the > option to display a roll like that anyways. Where the original notation (bottom version not produced by LilyPond) was: [2020-04-23.

Re: Drum notation and style

Hello Adrian, Being a drummer, I'm certain there is something wrong in the sticking off the roll the way you wrote it (see screen capture below) [cid:466e02cf-022d-4c6f-9e53-7a137f8740ef] I did a small example with the "unfolded roll" so you can see what I mean. Maybe what you want to do is t

Re: { } not sounding right.

> I rather thought about Lilypond being able to "look ahead|behind" > like (I imagine is working) the "Melody_Engraver" to harmonise (no > pun intended) the pitch shift up or down decision. > > \language "english" > > In my use case : > - the gqs is the note g pitched upward. > - the bqf is the