Re: Beam not breaking

Hi all, Never mind… I figured it out. Now on to the bug (?) I actually wanted to ask about. =) \version "2.23.4" { \time 1/4 \override Beam.breakable = ##t \override Beam.positions = #'(4 . 3) c'8 8[ \break 8] 8 } Is that expected output? Thanks, Kieren.

Beam not breaking

Hi all, Why is the Beam not breaking here? \version "2.23.4" { \time 1/4 \override Beam.breakable = ##t c'8[ \break 8] } Thanks, Kieren.

Re: Updating alists

Jean Abou Samra writes: > Le 30/12/2021 à 23:04, Lukas-Fabian Moser a écrit : >> Hi Jean, >> >>> >>> Both of these cases seem to work the same as in >>> current versions if I do >>> >>> [...] >>> >>>  SCM >>>  assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL) >>>  { >>> -  for (SCM p = alist

Re: Updating alists

Lukas-Fabian Moser writes: > Hi Jean, > >> >> Both of these cases seem to work the same as in >> current versions if I do >> >> [...] >> >>  SCM >>  assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL) >>  { >> -  for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p)) >> +  for (SCM p =

Re: Updating alists (was: Tenuto marking too close to note)

Le 30/12/2021 à 23:04, Lukas-Fabian Moser a écrit : Hi Jean, Both of these cases seem to work the same as in current versions if I do [...]  SCM  assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)  { -  for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p)) +  for (SCM p = alist;

Re: Updating alists (was: Tenuto marking too close to note)

Hi Jean, Both of these cases seem to work the same as in current versions if I do [...]  SCM  assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)  { -  for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p)) +  for (SCM p = alist; scm_is_pair (p) && scm_is_pair (scm_car (p)) && !sc

Re: Updating alists

Le 30/12/2021 à 22:30, David Kastrup a écrit : An empty list does not have a last cdr. Of course. Thanks.

Re: Updating alists

Jean Abou Samra writes: > Le 30/12/2021 à 12:36, Lukas-Fabian Moser a écrit : >> It's much worse than that: It's not the first time _I've_ been >> tripped up by this (previously it was with sort!). I'll just have to >> write 100 copies of >> >> "The exclamation mark in something! does not mean th

Re: Making a Lilypond donation (again)

I’ve contributed to David’s efforts in the past. I think this is an excellent idea. > On Dec 30, 2021, at 2:23 PM, Ivan Kuznetsov > wrote: > > I would like to make a onetime donation toward > the development of Lilypond. > > I have searched the archives of this list, and > over and over again

Making a Lilypond donation (again)

I would like to make a onetime donation toward the development of Lilypond. I have searched the archives of this list, and over and over again, it has been stated that there is no clear way to do this. At https://www.gnu.org/software/, Lilypond is listed as a "current GNU package", but can one do

Re: Updating alists (was: Tenuto marking too close to note)

Le 30/12/2021 à 12:36, Lukas-Fabian Moser a écrit : It's much worse than that: It's not the first time _I've_ been tripped up by this (previously it was with sort!). I'll just have to write 100 copies of "The exclamation mark in something! does not mean the function is guaranteed to make the

Re: 2.23.5 and poly-mark-engraver https://lsr.di.unimi.it/LSR/Item?id=976

On Dec 30, 2021, at 14:24, Lukas-Fabian Moser wrote: > > Hi Joel, > >> Several of the scores used poly-mark-engraver from >> (see also >> ), >> and this now fails with >> >>> fat

Re: 2.23.5 and poly-mark-engraver https://lsr.di.unimi.it/LSR/Item?id=976

Hello Joel, With 2.23 the MarkEvent gets replaced by the RehearsalMarkEvent and the AdHocMarkEvent, where the latter is meant for labeled and uncounted marks. This means that you you should replace 'MarkEvent in the polyMark function for 'AdHocMarkEvent or 'RehearsalMarkEvent, depending on

slash-only chords

Hi, I'm looking for a way to print a chord symbol which is a slash chord, but where the top part (above the slash) is blank. So, I only want to print the slash + root note. The usage for this is when the previous chord repeats, and only the bass note changes. Here is an MWE for a progression wh

Re: point-and-click default

Lukas-Fabian Moser writes: > Hi David, >> I've been using Lilypond for a few years, and only yesterday learned >> about the point-and-click feature in pdf output. In particular, I had >> no idea that by default Lilypond includes absolute pathnames to local >> source files on my system as metadat

Re: 2.23.5 and poly-mark-engraver https://lsr.di.unimi.it/LSR/Item?id=976

Hi Joel, Several of the scores used poly-mark-engraver from (see also ), and this now fails with fatal error: cannot find music object: MarkEvent (Minimal example below signat

Re: point-and-click default

Hi David, I've been using Lilypond for a few years, and only yesterday learned about the point-and-click feature in pdf output. In particular, I had no idea that by default Lilypond includes absolute pathnames to local source files on my system as metadata in the pdf output files. So when I upl

Re: point-and-click default

David Zelinsky writes: > Tom Sgouros writes: > >> For those of us just catching up, can someone explain how to see the >> metadata? I guess this is more of a PDF question, but while I have some >> experts' attention... >> >> Thank you, >> >> -Tom > > I can only tell you about evince, the pdf re

Re: \trill fails barcheck with articulate.ly

On 12/30/2021 6:40 AM, Lukas-Fabian Moser wrote: Am 30.12.21 um 04:10 schrieb Joel C. Salomon: Minimal example: \version "2.23.1" \include "articulate.ly" \articulate {     c''1\trill | } Is this something addressed between 2.23.1 (which I have installed) and 2.23.5 (current)? Yes, there's

2.23.5 and poly-mark-engraver https://lsr.di.unimi.it/LSR/Item?id=976

I'm returning to an old project (last touched in 2016) on a new computer, and I’m running 2.23.5 on Windows 11. Several of the scores used poly-mark-engraver from (see also ), and

Re: point-and-click default

Tom Sgouros writes: > For those of us just catching up, can someone explain how to see the > metadata? I guess this is more of a PDF question, but while I have some > experts' attention... > > Thank you, > > -Tom I can only tell you about evince, the pdf reader I use. But I expect it should be

Re: point-and-click default

Knute Snortum writes: > On Wed, Dec 29, 2021 at 7:13 PM David Zelinsky wrote: > [...] >> But even if it is configured to work, it seems like a REALLY BAD IDEA to >> have this feature enabled *by default*. Or, if it is to be the default, >> it ought to be mentioned VERY PROMINENTLY, so anyone in

Re: point-and-click default

For those of us just catching up, can someone explain how to see the metadata? I guess this is more of a PDF question, but while I have some experts' attention... Thank you, -Tom On Thu, Dec 30, 2021 at 10:25 AM Knute Snortum wrote: > On Wed, Dec 29, 2021 at 7:13 PM David Zelinsky > wrote: >

Re: point-and-click default

On Wed, Dec 29, 2021 at 7:13 PM David Zelinsky wrote: [...] > But even if it is configured to work, it seems like a REALLY BAD IDEA to > have this feature enabled *by default*. Or, if it is to be the default, > it ought to be mentioned VERY PROMINENTLY, so anyone installing and > using Lilypond w

Re: Updating alists

\version "2.23.6" myScripts = \default-script-alist myScripts.tenuto.padding = 5 \layout {   \context {     \Score     scriptDefinitions = #myScripts   } } {   a-- } (One might also skip defining a new variable and instead change default-script-alist directly, but it has to be re-read

Re: Updating alists

David Kastrup writes: > For stuff like > > > midiDrumPitches.ridecymbal = fis,, > midiDrumPitches.ridecymbala = b > midiDrumPitches.ridecymbalb = a > midiDrumPitches.crashcymbal = g > > > \midi > { > \context { > \Score > drumPitchTable = #(alist->hash-table midiDrumPitches) > } > } >

Re: Updating alists

Lukas-Fabian Moser writes: > Another question: With the (hopefully) upcoming changes in the > script-alist structure (using symbols instead of strings as keys), > we're quite close to being able to simply do > > \version "2.23.6" > > myScripts = \default-script-alist > myScripts.tenuto.padding =

Re: \trill fails barcheck with articulate.ly

Hi Joel, Am 30.12.21 um 04:10 schrieb Joel C. Salomon: Minimal example: \version "2.23.1" \include "articulate.ly" \articulate { c''1\trill | } Is this something addressed between 2.23.1 (which I have installed) and 2.23.5 (current)? Yes, there's no warning with 2.23.3 or higher. Lukas

Re: Relative Tempo Markings in Lilypond 2.22

Thanks, Carl. I didn't think about convert-ly. It's been a while since I needed it. dB On Wed, Dec 29, 2021, 11:10 PM Carl Sorensen wrote: > > > convert-ly will fix this for you. > > The argument for \note changed from a string ( #"8") to a duration > ({8}). See http://lilypond.org/doc/v2.22/

Updating alists (was: Tenuto marking too close to note)

Hi Jean, (CCing devel because of the stuff below the asterisks) Although this approach manipulates internal data structures of LilyPond, it has the advantage of dealing with your issue at the root and not causing side effects for other scripts. Unfortunately, this approach does not work direct

Re: point-and-click default

> > > This point-and-click seems like a useful feature for editing, *if* it's > configured to work on your system. But it apparently is not usually set > up that way by default, at least on most Linux systems. (I do > appreciate the instructions in the manual for configuring it, and plan > to do