Re: Conditional code in the midi block

Am So., 19. Mai 2024 um 21:28 Uhr schrieb Carolyn Beeton : > > I would like to include some Staff and Voice context settings in the \midi > block only if a flag is set to ##t and I have not been able to figure out how > to do this. When I try to wrap the \context blocks in a code block with >

New LSR snippet 1187 "New pitch language"

To the author of the new LSR snippet 1187 "New pitch language" https://lsr.di.unimi.it/LSR/Item?u=1=1187 You add your new language to "nederlands", thus \language "alpha" returns a warning: warning: Could not find language `alpha'. Ignoring. Please fix or delete that line. Furthermore, I think

Re: Empty chord construct and \break.

ly. Thank you so much!!! >> >> Hwaen Ch'uqi >> >> >> On Sun, Apr 28, 2024 at 7:24 AM Thomas Morley >> wrote: >>> >>> Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi >>> : >>> > >>> > Greetings, >>

Re: Empty chord construct and \break.

Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi : > > Greetings, > > I am trying to typeset a stack of spoken lines above a multimeasure rest. > This works fine when preceded by notes in the same system. However, when it > follows a forced break, the output is not so desirable. Can

Re: Special notation question

Am So., 21. Apr. 2024 um 17:43 Uhr schrieb Xavier Mayeur : > Hello, > > In a \time 3/2 score, how can I write the following snippet in Lilypond? > > > > I wonder how to create the 'g' note with that special appearance and with > the right duration... > > -- > Cordialement, > > Xavier MAYEUR >

Re: Multiple parts on the same stems

Am Di., 16. Apr. 2024 um 22:01 Uhr schrieb Gerardo Ballabio : > > Hello all, > I'm trying to typeset a percussion score with several instruments on > the same staff. When they play simultaneous notes I want to line them > up all on the same stem, like this (output attached, percussion1.pdf): > >

Re: Delayed turns etc

Am Mi., 17. Apr. 2024 um 11:13 Uhr schrieb Jean Abou Samra : > > That works for the last line of the whole score. The line I want to be > "ragged" is the last line of a page. with more music on the next page. > > > There is no way to make just one system ragged except the last one in the >

Re: make-music?

Am Sa., 13. Apr. 2024 um 22:09 Uhr schrieb Pierre-Luc Gauthier : > But what about the parenthesised alist -> (alist) ‽ > > I have not found documentation here : > https://extending-lilypond.gitlab.io/en/scheme/alists.html > nor here : >

Re: make-music?

Am Sa., 13. Apr. 2024 um 20:59 Uhr schrieb Pierre-Luc Gauthier : > > Hello there, > > Quite an easy one I'm sure but I tried many combinations to no avail. > > I have this symbol that I wish to evaluate later. I thought that was > what ly:make-music was for. > > \version "2.25.15" > > #(define

Re: Volta spanner missing edge when using "|" as endRepeatType

Am Do., 29. Feb. 2024 um 07:53 Uhr schrieb Andy Bradford : > > Hello, > > I want to place an interlude that happens only the first time through a > a section that has a repeat and a second interlude for the second time > through. I don't want the repeat measure bar showing up in the middle of >

Re: \partial and \compressMMRests don't seem to work together

Am Sa., 17. Feb. 2024 um 01:18 Uhr schrieb Gerardo Ballabio : > > Sorry, forgot the attachment. > > Il giorno sab 17 feb 2024 alle ore 01:15 Gerardo Ballabio > ha scritto: > > > > Hello, > > I need to change the time in the middle of a bar. > > I managed to do that using \partial, but it seems

Re: Table of Contents and mixed numbers.

Am Do., 15. Feb. 2024 um 19:16 Uhr schrieb Hwaen Ch'uqi : > > Greetings, > > Until upgrading to 2.24, I had been using certain Scheme code and > \paper block layouts in order to output books consisting of prefatory > material with Roman numeral page numbers and the music itself with > Arabic page

Re: Is there a property that would set all of the "above staff" text to "above chordnames"

Am Mo., 1. Jan. 2024 um 21:59 Uhr schrieb : > > On Mon, 1 Jan 2024, Kevin Cole wrote: > > > What I mean is, I often have a situation where there's only a wee bit > > o' text occasionally, above the staff. But I frequently have > > ChordNames. It seems to me that the ChordNames would be better

Problems while defining an aligning mark-spanner

Hi, please have a look at the code below. It is an attempt to implement an aligning spanner between certain marks at score-level. Here I use TextMark and a newly defined TextMarkSpanner-grob. Currently the TextNarks are moved, which is nice. Though, it relies on the highest element in the Staff,

Re: programming error: Improbable offset for stencil: -inf staff space,Setting to zero.

Am So., 19. Nov. 2023 um 15:30 Uhr schrieb Michael Gerdau : > > Hi lilyponders! > > the attached fairly short script creates 4x the aforementioned error. It > seems to be created by the combined >\tweak Parentheses.font-size #2 \parenthesize > > The resulting score looks basically fine

Re: LilyPond 2.25.10

Am Fr., 17. Nov. 2023 um 21:33 Uhr schrieb Michael Gerdau : > > >>> I will try to create a MWE if that is required to track down the > >>> problem. > >> > >> > >> A *minimal* example is not strictly required (though helpful), but > >> *some* example is — otherwise, there is nothing we can do,

Re: programming error: note-column has no direction

ere is any reason for not engraving the stems, but if there > isn’t I’d say the latter one is the more stable path. > > Cheers, > Valentin > > Am Samstag, 7. Oktober 2023, 10:35:20 CEST schrieb Thomas Morley: > > Hi, > > > > this came up in the german

programming error: note-column has no direction

Hi, this came up in the german forum: https://lilypondforum.de/index.php/topic,1280.msg6613.html A more minimel example: \version "2.24.2" %% \include "gregorian.ly" %% %% \layout { %% \context { %% \GregorianTranscriptionVoice %% \consists Stem_engraver %% \omit Stem %% } %% }

Re: Question about condensed score

Am Fr., 18. Aug. 2023 um 21:51 Uhr schrieb David Kastrup : > > Rip _Mus writes: > > > Hello, > > does anyone happen to have an answer? > > I just can't understand this behavior... > > > > Thank you > > > > Il mer 16 ago 2023, 08:18 Rip _Mus ha > > scritto: > > > >> Good morning everyone, > >>

Re: A query about tablature

Am Di., 8. Aug. 2023 um 11:14 Uhr schrieb Lukas-Fabian Moser : > > Hi Alasdair, > > > Thank you very much - that is quite amazing! > You're very welcome. > > But it does show what I have long suspected: that without some extra > > programming, Lilypond does not have a current facility to extract

Re: Retrieve context properties

Am So., 23. Juli 2023 um 10:03 Uhr schrieb Rip _Mus : > > Thank you Valentin, > this is very helpful! > The situation is that I always create a custom context, named "Tactus", that > creates bars for proportional notation (it's a Dynamics alias, that accepts > Voice and some overrides,

Re: In-staff fermata with 2.25.

Hi Jean, Am Mi., 7. Juni 2023 um 23:31 Uhr schrieb Jean Abou Samra : > > Le mercredi 07 juin 2023 à 23:07 +0200, Thomas Morley a écrit : > > Hi, > > this came up in the german forum: > https://lilypondforum.de/index.php/topic,1247.msg6512.html > > How to print f

In-staff fermata with 2.25.

Hi, this came up in the german forum: https://lilypondforum.de/index.php/topic,1247.msg6512.html How to print fermata _in_ staff with 2.25.? Below works with 2.24. \version "2.24.1" %#(ly:set-option 'debug-skylines #t) \layout { \override

Re: Circular staves

Am So., 23. Apr. 2023 um 04:38 Uhr schrieb Andrew Bernard : > > Just checking - you can't make circular staves with notes in lilypond, > can you? I know you can do nice circle of fifths diagrams as per an LSR > example, but circular staves are way out of scope, aren't they? > > This came up in the

Re: Bounding box for rotated markup

Am So., 9. Apr. 2023 um 12:16 Uhr schrieb Jean Abou Samra : > > > > > Le 9 avr. 2023 à 10:50, Thomas Morley a écrit : > > > > Hi, > > > > please consider following code: > > > > pol = \markup \polygon #'((0 . 2) (10 . 0) (10 . 20) (0 . 22)) &g

Bounding box for rotated markup

Hi, please consider following code: pol = \markup \polygon #'((0 . 2) (10 . 0) (10 . 20) (0 . 22)) \markup \override #'(box-padding . 0) \box { \pol \rotate #45 \pol } See attached image. How to get \box tight to the rotated polygon? Thanks, Harm

Re: Programming error with change staff

Am Do., 16. Feb. 2023 um 19:09 Uhr schrieb Knute Snortum : > > I have run into a situation where LilyPond produces a programming error. It > involves changing staff, voice one, accent fingering and avoid-slur. It's > best to just look at the MWE: > > \version "2.25.1" > > staffUp = \change

Re: Error in Extending Lilypond example

Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin : > > The fourth example engraver here: > https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example > > Running this code in 2.24 crashes on initializing the engraver with In > procedure

Re: Completion_heads_engraver for line-ends only?

Am Di., 17. Jan. 2023 um 18:32 Uhr schrieb Graham King : > > I'm preparing an edition of de Wert's motet "Ascendente Jesu in naviculam" > which has an extended stretto section with dotted rhythms across barlines. > For this, Harm's Mensurstriche example in the Learning Manual produces a >

Re: Resize \rhythm in mixed markup

Am Di., 10. Jan. 2023 um 02:44 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley > > : > >> > >> Hi, > >> > >> consider below > >> > >> \version

Re: Resize \rhythm in mixed markup

Am So., 8. Jan. 2023 um 11:13 Uhr schrieb Thomas Morley : > > Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley > : > > > > Hi, > > > > consider below > > > > \version "2.24.0" > > > > \score { > > { g'1^\

Re: Resize \rhythm in mixed markup

Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley : > > Hi, > > consider below > > \version "2.24.0" > > \score { > { g'1^\markup { My Rhythm \rhythm { 8[ 8] } } } > \layout { > \context { > \StandaloneRhythmStaff > fontS

Resize \rhythm in mixed markup

Hi, consider below \version "2.24.0" \score { { g'1^\markup { My Rhythm \rhythm { 8[ 8] } } } \layout { \context { \StandaloneRhythmStaff fontSize = #6 } } } I'll have numerous such markups combining straight text and \rhythm. Thus I'd like to have a method to adjust

Re: How to get log only

Am Fr., 23. Dez. 2022 um 15:53 Uhr schrieb Jean Abou Samra : > > Le 23/12/2022 à 10:35, Thomas Morley a écrit : > > Hi, > > > > while debugging some files I'm interested in the log only, thus I'd > > like to avoid creating any other output. > >$ lil

How to get log only

Hi, while debugging some files I'm interested in the log only, thus I'd like to avoid creating any other output. $ lilypond -dlog-file=AAALOG --formats=#f -ddelete-intermediate-files file-1.ly file-2.ly still returns .ps-files. What's the correct command? Thanks, Harm

Re: "loco" after ottava

Am Sa., 3. Dez. 2022 um 16:56 Uhr schrieb Jean Abou Samra : > > Le 03/12/2022 à 15:41, Thomas Morley a écrit : > > Granted, if I use -dcheck-internal-types I mostly wear my developer > > hat. But sometimes I use it even for huge custom codings as part of > > debugging proc

Re: Different default arpeggio positions

Am Sa., 3. Dez. 2022 um 16:35 Uhr schrieb Jean Abou Samra : > > Le 03/12/2022 à 15:58, Thomas Morley a écrit : > > Ofcourse. Though, it's another thing a (probably new) user has to > > learn, maybe scaring him/her away. > > > For someone coming from a language like Ha

Re: Different default arpeggio positions

Am Sa., 3. Dez. 2022 um 13:41 Uhr schrieb Jean Abou Samra : > > Le 02/12/2022 à 23:47, Thomas Morley a écrit : > > I know you like pattern matching, though imho it makes things not > > always easier for users. > > > > Yes, I like pattern matching. No, I'm not going

Re: "loco" after ottava

Am Sa., 3. Dez. 2022 um 15:06 Uhr schrieb Jean Abou Samra : > -S only shows commits that changed the number of occurrences > of the pattern, which is useful to find out when something > was added or deleted. To find all the times a line containing > the pattern was changed, use -G instead.

Re: "loco" after ottava

Am Sa., 3. Dez. 2022 um 13:53 Uhr schrieb Jean Abou Samra : > Le 03/12/2022 à 13:26, Thomas Morley a écrit : > > \version "2.23.0" > > > 2.23.80, I suppose? horizontal-line-spanner is new in 2.23.6. Ofcourse, that 8 slipped away somehow... > > Btw, I

Re: "loco" after ottava

Am Fr., 2. Dez. 2022 um 02:28 Uhr schrieb Joel C. Salomon : > > Piece of music I have in front of me puts the text "loco." above the > first note after an ottava. See also the attached example, from > . > > The code below does not work, which makes me

Re: Different default arpeggio positions

Am Fr., 2. Dez. 2022 um 11:46 Uhr schrieb Jean Abou Samra : > > Le 02/12/2022 à 05:16, Abraham Lee a écrit : > > Code works perfectly, Jean, though what it's doing is a bit of a > > mystery. You've been very kind to provide a solution and I don't want > > to take more of your time on the subject,

Re: Different default arpeggio positions

Hi Jean, Am Do., 1. Dez. 2022 um 09:48 Uhr schrieb Jean Abou Samra : > This is a widespread but bad coding pattern that I regularly advise > against on this list :-) you'll find a plethora of snippets in the archives using after-line-breaking authored by me. Likely starting in 2.12.3. > It

Re: table-of-contents for multiple books per ly-file

Am Sa., 19. Nov. 2022 um 14:48 Uhr schrieb Jean Abou Samra : > > Le 19/11/2022 à 14:43, Thomas Morley a écrit : > > Though, I can't use a modified version of the new code setting > > `toc-items' because dong so in an own ly-file causes: > > fatal error: call-after-session

table-of-contents for multiple books per ly-file

Hi, this is about #4227 "Tables of contents are not independent between \books" https://gitlab.com/lilypond/lilypond/-/issues/4227 My previous workaround was to abuse the 'name entry in each toc-item, i.e. I used a custom `tabel-of-contents'-markup-command filtering `toc-items' for a certain

Re: MetronomeMark and break-visibility

Am Di., 1. Nov. 2022 um 16:30 Uhr schrieb Jean Abou Samra : > > Le 01/11/2022 à 12:55, Thomas Morley a écrit : > > Hi, > > > > the following code for _Rehearsal_Mark works as expected, i.e. the > > RehearsalMark is printed at end of line: > &

MetronomeMark and break-visibility

Hi, the following code for _Rehearsal_Mark works as expected, i.e. the RehearsalMark is printed at end of line: { b1 \override Score.RehearsalMark.break-visibility = ##(#t #f #f) \mark \default \break b } Alas, the same for _Metronome_Mark fails, the MetronomeMark is not printed at

Re: Passing a parameter to Scheme

Am Sa., 29. Okt. 2022 um 12:32 Uhr schrieb Paul Hodges : > > On further thought, I suspect that I can't aim at "\speak #-3.8 c" because > #-3.8 isn't a music expression so LilyPond won't let me. I guess I'll need > to use a \tweak or \set on the parameter variable instead. But that leaves >

Re: Appoggiatura in bass clef at start of piece

Am Mi., 26. Okt. 2022 um 19:27 Uhr schrieb Peter Mitton : > > Hi, > > I’m wondering if there is a better way of writing this code: > > \version "2.22.2" > > \new Staff { > << > % \time 6/8 > % \clef bass > \new Voice = "a" { >

Re: another 'wrong type argument' error

Am Mi., 12. Okt. 2022 um 11:37 Uhr schrieb Thomas Morley : > > Am Mo., 10. Okt. 2022 um 21:04 Uhr schrieb Kieren MacMillan > : > > > > Hi Jean, > > > > > This looks like you have done something like > > > { c'\custdyn "p" } > > > in

Re: another 'wrong type argument' error

Am Mo., 10. Okt. 2022 um 21:04 Uhr schrieb Kieren MacMillan : > > Hi Jean, > > > This looks like you have done something like > > { c'\custdyn "p" } > > instead of > > { c'\custdyn "{p}" } > > Hmmm… the only three calls I have look like the second (correct) version, not > the first. But switching

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

Re: Accent on single note of chord?

Am Sa., 24. Sept. 2022 um 22:44 Uhr schrieb Jean Abou Samra : > > > > Le 24/09/2022 à 22:34, Andy Bradford a écrit : > > Thus said Jean Abou Samra on Sat, 24 Sep 2022 22:17:26 +0200: > > > >> Are you asking this because you saw this notation in a printed score, > >> or because you want to use it

Re: Alphabetised table of contents?

Am Mi., 21. Sept. 2022 um 07:41 Uhr schrieb Jean Abou Samra : > > Le 21/09/2022 à 07:09, Werner LEMBERG a écrit : > > [*] Except Jean has time and interest to produce a solution like pulling > > a rabbit out of a hat :-) > > > I do have a rabbit to pull out, because I actually already posted

Re: tremolo w/dots

Am So., 4. Sept. 2022 um 15:46 Uhr schrieb bobr...@centrum.is : > > Does LilyPond know how to do this without resorting to using \markup? The > dots over the stemDown note also looks too far right. I could adjust it on a > case-by-case basis but that seems rather tedious if LilyPond can do

Re: Alternative to Frescobaldi

Am So., 4. Sept. 2022 um 08:51 Uhr schrieb Silvain Dupertuis : > > As far as editing music sheet is concerned,Io remember having been using > jEdit, a text editor written in Java, with a Lilypond extension displaying > the PDF with links to the Lilypond code like Frescobaldi does it. > > That

Re: docs about Rest vertical position

Am Fr., 2. Sept. 2022 um 21:44 Uhr schrieb Jean Abou Samra : > [...] moving \rest to a footnote or undocumenting it altogether. > Whether its outright removal is desirable is another question. > > This is veering into lilypond-devel territory, maybe we should continue the > discussion there?

Re: Barre grob - appearance

Am Mo., 29. Aug. 2022 um 23:24 Uhr schrieb Jean Abou Samra : > > Le 27/08/2022 à 13:55, Thomas Morley a écrit : > > I foresee some hard to solve problems, though. I'm currently not sure > > about the success. > > > IUUC, you have a problem to draw the grob with both a

Re: Barre grob - appearance

Am Mo., 29. Aug. 2022 um 23:20 Uhr schrieb Jeff Olson : > > > On 8/27/2022 5:36 AM, Thomas Morley wrote: > > Ofcourse, one can find several > > codings here on the list, in LSR, I have some own as well. All are > > (ab)using spanners like TextSpanner or hijacking ot

Re: Barre grob - appearance

Am Sa., 27. Aug. 2022 um 13:47 Uhr schrieb Andrew Bernard : > > When you complete this work, would you like to add it to OpenLilyLib? > > Andrew If I'm able to finish it, I plan to put up a patch to get it into the source. I foresee some hard to solve problems, though. I'm currently not sure

Barre grob - appearance

Hi all, being a professional guitarist I always missed a possibility to use a barré-sign which fits all needs. Ofcourse, one can find several codings here on the list, in LSR, I have some own as well. All are (ab)using spanners like TextSpanner or hijacking other grobs like Arpeggio. Though, we

Re: Customizing tremolo

Am So., 21. Aug. 2022 um 21:55 Uhr schrieb Werner LEMBERG : > > > > Maybe it's worth to at least extend the doc tagged lsr snippet > > "Engraving tremolos with floating beams" > > https://lsr.di.unimi.it/LSR/Item?id=553 > > I think this is rather a bug that should be fixed, so please open an >

Re: Customizing tremolo

Am So., 21. Aug. 2022 um 13:10 Uhr schrieb Thomas Morley : > > Hi, > > this arose in the german forum about typesetting tremolos for > https://imslp.org/wiki/String_Quartet_(Carre%C3%B1o%2C_Teresa). > https://lilypondforum.de/index.php/topic,1091.msg5888.html > An excerp

Customizing tremolo

Hi, this arose in the german forum about typesetting tremolos for https://imslp.org/wiki/String_Quartet_(Carre%C3%B1o%2C_Teresa). https://lilypondforum.de/index.php/topic,1091.msg5888.html An excerpt of Vl 2 is attached. In measure 8 there are tremolos with one connecting beam and one floating

Re: polychords: what's the current state-of-the-art?

Am Mo., 8. Aug. 2022 um 22:07 Uhr schrieb Kieren MacMillan : > > Hi all, > > What's the current best snippet for rendering polychords? I know the GSoC > chord stuff is still in air traffic control, but the snippet found at >

Re: Learning Lilypond internals

Am Fr., 12. Aug. 2022 um 07:45 Uhr schrieb Andrew Bernard : > > Although I have long experience in software development, the Lilypond source > is a body of work that I have never really been able to comprehend. This is a > pity as I always wanted to help with development. Now, when I have

Re: Markup in ChordNames context

Am Sa., 13. Aug. 2022 um 07:47 Uhr schrieb Jean Abou Samra : > > Le 13/08/2022 à 01:02, Peter Chubb a écrit : > > Hi, > > Sometimes in vocal+ukulele music I want to indicate that a > > particular chord uses an alternate fingering. I'd like to add > > an asterisk and a footnote

Re: An infix syntax for Scheme ...

Am Di., 9. Aug. 2022 um 23:46 Uhr schrieb Jean Abou Samra : > > Hi, > > Some time ago, Jacques Menu asked on the French-speaking equivalent of > this list if it would be possible to create an infix syntax for Scheme > that would be more approachable for beginners. > > As we discussed this topic

Re: Glissando stems

Am Mo., 8. Aug. 2022 um 16:35 Uhr schrieb Mark Knoop : > > Following on from this old thread... > > https://lists.gnu.org/archive/html/lilypond-user/2019-10/msg00405.html > > ... I'm using Harm's fantastic code to align/attach Stems to a Glissando line. > > However, I've come across a problem with

Re: vertical shift of trill

Am Sa., 6. Aug. 2022 um 17:15 Uhr schrieb Jean Abou Samra : > > Le 06/08/2022 à 16:45, Werner LEMBERG a écrit : > >> That said, there's a much simpler way. [...] > > Your solution is ingenious. However, how on earth are we mere mortals > > able to find that? > > > Read the source, Luke :-)

Re: Ties between voices

Am Di., 26. Juli 2022 um 11:48 Uhr schrieb Thomas Morley : > > Am Sa., 23. Juli 2022 um 19:15 Uhr schrieb Jean Abou Samra > : > > > > > > > > Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit : > > > > > > Hi Andrew, > > > > > &g

Re: Ties between voices

Am Sa., 23. Juli 2022 um 19:15 Uhr schrieb Jean Abou Samra : > > > > Le 23/07/2022 à 12:49, Lukas-Fabian Moser a écrit : > > > > Hi Andrew, > > > > Am 23.07.22 um 03:49 schrieb Andrew Bernard: > >> I know that we can't natively make ties between notes in different > >> voices. I know that there

Re: Going back in MIDI time

Am Mo., 25. Juli 2022 um 11:05 Uhr schrieb Mario Moles : > > Hi lilponders! > > Do you know how to eliminate this warning? I have not found anything > either on the list or on google: > "programming error: Going back in MIDI time. > go on, cross your fingers " > > Thanks > > Haven't seen this for

Re: \vshape and custom curve-stencil for TextSpanner

Am Sa., 23. Juli 2022 um 16:06 Uhr schrieb Jean Abou Samra : > > Hi Harm, > > > Le 23/07/2022 à 10:59, Thomas Morley a écrit : > > I'm attempting to create a s-curve stencil for TextSpanner. > > While so far all works as wished and it is possibel to use \shape

\vshape and custom curve-stencil for TextSpanner

Hi, I'm attempting to create a s-curve stencil for TextSpanner. While so far all works as wished and it is possibel to use \shape, \vshape doesn't print the control-points. What am I missing? Code below. Thanks to Jean how fixed make-path-stencil! Thanks, Harm \version "2.23.11" #(define

Re: problem with global-staff-size and book bloks

Am Fr., 22. Juli 2022 um 08:21 Uhr schrieb Reuben Kagan : > > Hi, > > here is my example : > \version "2.22.2" > %file NOTES.ly > > #(set-global-staff-size 10) > NOTES = \relative c'' { >\key d \minor \time 3/4 >a bes c d e f > } > > \score { >\new Staff \NOTES > } > > \book { >

Re: Dashed Stem Fontsize !

Am Fr., 22. Juli 2022 um 13:04 Uhr schrieb Ya Gloops : > > > Hello ! I try to keep the proportion of the "dashed-stem" but I can't... If > someone can help me. > Gilles > > \version "2.23.10" > > > %#(set-global-staff-size 30) > > > #(define (make-round-filled-box x1 x2 y1 y2 blot-diameter) >

Re: Undertie in lyrics to show no breath

Am Mi., 20. Juli 2022 um 15:18 Uhr schrieb mancunius : > > Hello. In the following example I want the undertie to be placed between the > 2 “O sacrum convivium” lines of lyrics, to indicate that no breath should be > taken by the singers - as per the normal choral convention. (cf. the >

Re: Snippet doesn't work in unstable version

Am Mi., 20. Juli 2022 um 18:43 Uhr schrieb Martín Rincón Botero < martinrinconbot...@gmail.com>: > Hello, > > I grabbed this snippet a while ago from somewhere™ which puts a box > around music (an "improvisation box"). It works perfectly in Lilypond > 2.22.1, but not in Lilypond 2.23.3+. Does

Re: Snippet doesn't work in unstable version

Am Mi., 20. Juli 2022 um 18:43 Uhr schrieb Martín Rincón Botero < martinrinconbot...@gmail.com>: > Hello, > > I grabbed this snippet a while ago from somewhere™ which puts a box > around music (an "improvisation box"). It works perfectly in Lilypond > 2.22.1, but not in Lilypond 2.23.3+. Does

Re: Moving a tie in a chord

Am Mi., 20. Juli 2022 um 02:17 Uhr schrieb Knute Snortum : > > I'm trying to adjust the Y position of a tie in a chord, but I'm > having trouble. What works for a single tie doesn't seem to work for > a chord: > > %%% > \version "2.22.2" > > moveTie = { > \once \override Tie.staff-position = -5

Re: Change to \rest markup in 2.23

Am Mi., 20. Juli 2022 um 14:29 Uhr schrieb David Kastrup : > > David Kastrup writes: > > > Jean Abou Samra writes: > > > >> Le 20/07/2022 à 05:57, David F. a écrit : > >>> In 2.23, the rest markup command changed from taking a string to taking a > >>> duration. > >>> > >>> \version "2.22" > >>>

Re: Change to \rest markup in 2.23

Am Mi., 20. Juli 2022 um 05:58 Uhr schrieb David F. : > > In 2.23, the rest markup command changed from taking a string to taking a > duration. > > \version "2.22" > \markup \rest #"4.." > > \version "2.23" > \markup \rest { 4.. } > > It would be nice if this change were backward compatible, at

Re: debug scheme part working with Frescobaldi

Am Di., 19. Juli 2022 um 21:40 Uhr schrieb Eef Weenink : > > So I am start working with scheme parts in my liypond files (using > arranger.ly). Using Frescobalid to input all > When compiling I keep getting messages: > > GUILE signaleerde een fout voor de hier beginnende expressie > > It would be

Re: Code pointer from end-BarLine to previous NoteHead.?

Am Mo., 18. Juli 2022 um 18:43 Uhr schrieb Lukas-Fabian Moser : > > Forgive me for piping up: > > I'm not able to say what happened, I'm not able to debug because of > > that unhelpful (oh, I'm very polite this evening) guile messages, see > > the other thread. > > > > I'm overtired like hell,

Re: Installing Lilypond 2.23.10

Am Mo., 18. Juli 2022 um 11:16 Uhr schrieb Jean Abou Samra : > > Le 17/07/2022 à 17:03, David Sumbler a écrit : > > At the moment I am testing it on a short file - in fact, your > > "grow-in-up-direction" example from the Extending Lilypond document. > > Compiling it is taking over 80 seconds

Re: error handling

Am Mo., 18. Juli 2022 um 11:02 Uhr schrieb Jean Abou Samra : > > Le 17/07/2022 à 23:33, Thomas Morley a écrit : > > Sorry for the delayed reply! > > I now tried to make some steps for scm-files/ly:load/autocompile. > > > > Though, as far as I can tell ly:load doe

Re: lilypond-book texinfo and a two-book-ly-file

Am Sa., 9. Juli 2022 um 13:41 Uhr schrieb Thomas Morley : > (2) One of the books is in portrait the other in landscape format > Is there any texinfo option to get the landscape one rotated? > That landscape thingy is needed and I can't change it, it may be an > option to drop the p

Re: Code pointer from end-BarLine to previous NoteHead.?

Am So., 17. Juli 2022 um 09:26 Uhr schrieb Jean Abou Samra : > > > > Le 17/07/2022 à 01:25, Thomas Morley a écrit : > > Thanks for your explanations, right now I had only a quick glance over > > them. > > I'll hopefully have some time soon to dive into it... >

Re: error handling

Am Mi., 6. Juli 2022 um 19:07 Uhr schrieb Jean Abou Samra : > > > > On 7/5/22 01:10, Thomas Morley wrote: > > Am Di., 5. Juli 2022 um 00:34 Uhr schrieb Jean Abou Samra > > : > > > > I just detected I can't compile my code with 2.22. any more, due to >

Re: Code pointer from end-BarLine to previous NoteHead.?

Am So., 17. Juli 2022 um 09:26 Uhr schrieb Jean Abou Samra : > > > > Le 17/07/2022 à 01:25, Thomas Morley a écrit : > > Thanks for your explanations, right now I had only a quick glance over > > them. > > I'll hopefully have some time soon to dive into it... >

Re: Code pointer from end-BarLine to previous NoteHead.?

Am Sa., 16. Juli 2022 um 23:12 Uhr schrieb Jean Abou Samra : > > Le 16/07/2022 à 20:47, Thomas Morley a écrit : > > Hi Jean, > > thanks for the hint. > > Alas, the code below _ensures_ the NoteHead _before_ the BarLine is > > taken (if I'm wrong here, I

Re: Code pointer from end-BarLine to previous NoteHead.?

Am Sa., 16. Juli 2022 um 14:05 Uhr schrieb Jean Abou Samra : > > > > > Le 16 juil. 2022 à 13:01, Thomas Morley a écrit : > > > > Hi, > > > > I'm trying to code an engraver setting a pointer from BarLine to > > previous NoteHead and an override for

Code pointer from end-BarLine to previous NoteHead.?

Hi, I'm trying to code an engraver setting a pointer from BarLine to previous NoteHead and an override for BarLine.Y-offset acting upon that pointer. It does not work, if the BarLine is at end. Here a stripped down example (every security is removed and all is heavily simplified):

Re: lilypond-book texinfo and a two-book-ly-file

Am Sa., 9. Juli 2022 um 16:44 Uhr schrieb Jean Abou Samra : > > > > Le 09/07/2022 à 13:41, Thomas Morley a écrit : > > Hi, > > > > for some huge custom code I'm going to write some documentation using > > texinfo. > > I started to se

lilypond-book texinfo and a two-book-ly-file

Hi, for some huge custom code I'm going to write some documentation using texinfo. I started to set up the file manual.tely. In terminal then: lilypond-book manual.tely texi2html manual.texi At some point I have: @lilypondfile[quote]{../doc-snippets/haenschen-klein.ly} Two questions

Re: error handling

Am Di., 5. Juli 2022 um 00:34 Uhr schrieb Jean Abou Samra : I just detected I can't compile my code with 2.22. any more, due to the internal changes in \repeat volta. Ofcourse it could have been any other change as well. Should I code for both lily-versions, just to get helpful error messages?

error handling

Currently I'm doing some huge scheme-coding. Again and again I get error messages like: $ lilydevel event-chords.ly GNU LilyPond 2.23.9 (running Guile 2.2) [...] Processing `event-chords.ly' Parsing...srfi/srfi-1.scm:432:2: In procedure last: In procedure car: Wrong type argument in position 1

Re: Access header-modules from inside markup-command

Am Mo., 27. Juni 2022 um 13:23 Uhr schrieb Jean Abou Samra : > > > > Le 27/06/2022 à 12:12, Thomas Morley a écrit : > > Hi, > > > > https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to > > access header-entries for use in arbitrary markup. >

Access header-modules from inside markup-command

Hi, https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to access header-entries for use in arbitrary markup. Alas it's limited to $defaultheader. Although there is a comment to add/access other headers like from \score, \bookpar explicit \book, I found no way to do so. I tried to

  1   2   3   4   5   6   7   8   9   10   >