Re: Lyric extender in RhythmicStaff

Le 08/10/2022 à 21:10, Lukas-Fabian Moser a écrit : Why is there no LyricExtender in the RhythmicStaff? What's missing? (Followup question: Is this behaviour intended?) I suggest to open an issue. Jean

Re: Table-of-contents subheadings on separate pages

Hello Brent, you could try to go for separate tocs for each subheading, like this: \version "2.22.2" #(define (symbol-or-false-or-procedure? x) (or (symbol? x) (not x) (procedure? x))) %% Copied from LilyPond's definition and modified % @param printtitle If #f no title is printed % @param filt

Re: Solfege Syllables Easy Notes

If you really want to muse, muse about rhythm syllables.   Kodaly rhythm syllables are iffy.  Gordon syllables have syntax and account for unusual meters.  I remember getting yelled at during a meeting of music teachers when I gave a demonstration of Gordon rhythm syllables.  That's how fucked

Re: Solfege Syllables Easy Notes

Hi Craig, > If you really want to muse, muse about rhythm syllables. Kodaly rhythm > syllables are iffy. Gordon syllables have syntax and account for unusual > meters. I remember getting yelled at during a meeting of music teachers when > I gave a demonstration of Gordon rhythm syllables.

Re: Solfege Syllables Easy Notes

Craig Bakalian writes: > If you really want to muse, muse about rhythm syllables.   Kodaly > rhythm syllables are iffy.  Gordon syllables have syntax and account > for unusual meters.  I remember getting yelled at during a meeting of > music teachers when I gave a demonstration of Gordon rhythm >

another 'wrong type argument' error

Hi again, Something still isn't working with a few of my scores, and I'm hoping someone can once again point me in the right direction for a quick fix… (No, a MWE isn't a real option.) — I'm running Lilypond 2.23.13 (installed via MacPorts) on macOS 10.13.6 (High Sierra) — I believe used conve

Re: Solfege Syllables Easy Notes

Yes, takadimi (kind of esperanto made of konnakal, kodaly and others. http://www.takadimi.net/documents/Takadimi%20short%20guide%20for%20Web.pdf Op 9 okt. 2022, om 17:57 heeft Craig Bakalian mailto:craigbakal...@gmail.com>> het volgende geschreven: If you really want to muse, muse about rhythm

Re: another 'wrong type argument' error

Hi Kieren, Le 09/10/2022 à 19:38, Kieren MacMillan a écrit : Hi again, Something still isn't working with a few of my scores, and I'm hoping someone can once again point me in the right direction for a quick fix… (No, a MWE isn't a real option.) — I'm running Lilypond 2.23.13 (installed vi

Re: another 'wrong type argument' error

Kieren MacMillan writes: > Anyone know where I should be looking to find the culprit? git grep list-head suggests woodwind diagrams, predefined fretboards, the function offset-fret, the \parallelMusic construct as possible callers. Anything in that list? If not, my guess would be some edition

Re: another 'wrong type argument' error

Hi David, > git grep list-head > > suggests woodwind diagrams, predefined fretboards, the function > offset-fret, the \parallelMusic construct as possible callers. > > Anything in that list? I doubt it… > If not, my guess would be some edition-engraver > code when taking into account your usua

Re: another 'wrong type argument' error

Hi again, D'oh… The better implication for me to have gotten from your helpful email would have been to search for "list-head" in all the files in my path/folder… Here's the output of that effort: [from OLL] edition-engraver/engine.scm:623:) (wildcard2regex (list-tail (list-hea

Re: another 'wrong type argument' error

Am So., 9. Okt. 2022 um 20:51 Uhr schrieb Kieren MacMillan : > > Hi David, > > > git grep list-head > > > > suggests woodwind diagrams, predefined fretboards, the function > > offset-fret, the \parallelMusic construct as possible callers. > > > > Anything in that list? > > I doubt it… > > > If not,

Re: another 'wrong type argument' error

Kieren MacMillan writes: > Hi again, > > D'oh… The better implication for me to have gotten from your helpful > email would have been to search for "list-head" in all the files in my > path/folder… > > Here's the output of that effort: > > [from OLL] > edition-engraver/engine.scm:623: ) (wildcard

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 21:19, David Kastrup a écrit : > > No idea. Most can be ruled out, and for the other two one would have to > look at more context. > > It's really a clumsy way to debug. Not the least because the use of list-head could also be somewhere in Guile itself. For example, i

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 21:19, David Kastrup a écrit : > > Let's hope that better error > pinpointing starts working soonish. Heh, 2.23.14 _just_ came out. https://gitlab.com/lilypond/lilypond/-/releases Kieren, try using that and putting #(ly:set-option 'compile-scheme-code) at the top of you

Control of horizontal space in score

Hi! Is it possible to control the horizontal space, i.e. I would like to define that a beat occupies the same space, whether is composed by 1 quarter-note or by 2 16th-note or by 4 32th-note.

Re: another 'wrong type argument' error

Hi all, > Heh, 2.23.14 _just_ came out. > https://gitlab.com/lilypond/lilypond/-/releases > > Kieren, try using that When I download and unzip it, Frescobaldi doesn't like it: I'm assuming it’s a 64-versus-32-bit issue? (I'm working on a 2011

Re: Control of horizontal space in score

António Sá Pinto writes: > Hi! > Is it possible to control the horizontal space, i.e. I would like to define > that a beat occupies the same space, whether is composed by 1 quarter-note > or by 2 16th-note or by 4 32th-note.

Re: another 'wrong type argument' error

Hi Harm, > What happens if you follow the comments below? Cheers, Harm > >> ;; Next line should be used for 2.19.65 and above >> ;(ly:grob-set-property! grob 'stencil >> ; (stack-stencils X RIGHT 0 all-stils)) >> ;; This line is for 2.18.2,

Re: another 'wrong type argument' error

Le 09/10/2022 à 22:24, Kieren MacMillan a écrit : Hi all, Heh, 2.23.14 _just_ came out. https://gitlab.com/lilypond/lilypond/-/releases Kieren, try using that When I download and unzip it, Frescobaldi doesn't like it: [image] I'm assuming it’s a 64-versus-32-bit issue? (I'm working on a 2011

Re: another 'wrong type argument' error

Hi Jean, > If you type "~/Downloads/lilypond-2.23.14/bin/lilypond" in a terminal, > what does it give? dyld: Symbol not found: _iconv Referenced from: /usr/lib/libcups.2.dylib Expected in: /opt/local/lib/libiconv.2.dylib in /usr/lib/libcups.2.dylib Abort trap: 6 > Also, how did you install

Re: another 'wrong type argument' error

On Sun, 2022-10-09 at 16:24 -0400, Kieren MacMillan wrote: > Hi all, > > > Heh, 2.23.14 _just_ came out. > > https://gitlab.com/lilypond/lilypond/-/releases > > Kieren, try using that > > > When I download and unzip it, Frescobaldi doesn't like it: > > > I'm assuming it’s a 64-versus-32-bit is

Re: another 'wrong type argument' error

Hi Jonas, > Probably not since all Intel Core processors should be 64-bit. It's > more likely that you are also running an ancient version of macOS. Oh, for sure: macOS 10.13.6 (the maximum this old iMac will run). > running an outdated and insecure operating system is bad by itself... The mome

LilyPond 2.23.14

We are happy to announce the release of LilyPond 2.23.14. This is termed a development release, but these are usually reliable. However, if you require stability, we recommend using version 2.22.2, the current stable release. Please refer to the Installing section in the Learning Manual for instruc

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 22:52, Kieren MacMillan a > écrit : > > The moment I can afford a new computer for my studio, I'll upgrade! Apart from buying new hardware, you could also run the Linux binaries in a Linux VM. Jean

Re: another 'wrong type argument' error

Jean Abou Samra writes: >> Le 9 oct. 2022 à 22:52, Kieren MacMillan >> a écrit : >> >> The moment I can afford a new computer for my studio, I'll upgrade! > > > Apart from buying new hardware, you could also run the Linux binaries > in a Linux VM. I would be surprised if a 64bit Linux would be

Re: another 'wrong type argument' error

The computer under discussion (2011 Intel Core i7 iMac) has a 64 bit architecture and Mac OS 10.13 is 64 bit (Mac OS has had a 64 bit option since 10.6 and 10.8 removed the 32 bit kernel). This definitely isn’t likely to be a 64/32bit issue - I think that’s some kind of confusion. However, is

Re: another 'wrong type argument' error

Confirmed using otool that the minimum OS for the linked build is 10.15: Load command 10 cmd LC_BUILD_VERSION cmdsize 32 platform 1 minos 10.15 sdk 10.15.6 That is certain to be the reason why it doesn’t run, but I suspect a local build might run fine. I’d suggest setting this

Re: another 'wrong type argument' error

Hi Alex, > Confirmed using otool that the minimum OS for the linked build is 10.15: > > Load command 10 > cmd LC_BUILD_VERSION > cmdsize 32 > platform 1 > minos 10.15 > sdk 10.15.6 Oh! Fascinating. Thanks for digging that up. Kieren.

Re: another 'wrong type argument' error

> Confirmed using otool that the minimum OS for the linked build is > 10.15: > > Load command 10 > cmd LC_BUILD_VERSION > cmdsize 32 > platform 1 > minos 10.15 > sdk 10.15.6 Thanks. > That is certain to be the reason why it doesn’t run, but I suspect a > local build might run

Re: another 'wrong type argument' error

> Le 10 oct. 2022 à 07:10, Werner LEMBERG a écrit : > >> That is certain to be the reason why it doesn’t run, but I suspect a >> local build might run fine. I’d suggest setting this lower for >> binary releases if there’s no pressing reason to require 10.15 on >> Mac. > > Sounds sensible. Jo

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 22:45, Kieren MacMillan a > écrit : > > dyld: Symbol not found: _iconv > Referenced from: /usr/lib/libcups.2.dylib > Expected in: /opt/local/lib/libiconv.2.dylib > in /usr/lib/libcups.2.dylib > Abort trap: 6 What surprises me in this error message is that mentions a dy