Re: how difficult would it be to have “auto-correct spacing” (even for just a single measure)?

>> You are aware of https://lsr.di.unimi.it/LSR/Item?id=1154 ? > > Oh! I vaguely recall that. Thanks for the reminder. > > I believe I applied it to my score, but it didn‘t make a change in > m7. It might be because of the accidentals…? (See modified snippet > acting as MWE, below.) Unfortunatel

Re: how difficult would it be to have “auto-correct spacing” (even for just a single measure)?

> If you look at the first measure of the third system, you can see > that the note spacing is distorted by various things (lyrics, > accidentals, etc.). But clearly there’s more than enough horizontal > room to make those eighth notes absolutely even — in fact, that kind > of thing is what the ma

Re: Frescobaldi... panic alternatives?

>> Maybe one of you two can provide some text for >> >>https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > It happens that my first contribution to the Lilypond documentation > was a rewrite of the Easier Editing section, some 14 years ago or > so. Aaah :-) > If either or b

Re: Frescobaldi... panic alternatives?

> Yes, I also use that combo. It's fantastic, but you'd have to be > willing to invest some time to climb the admittedly steep learning > curve of (neo)vim. However, it's a time investment that pays off > massively, so I recommend it heartily! Maybe one of you two can provide some text for ht

Re: Frescobaldi ... panic alternatives?

> With not too much work, you could get emacs to do all of that I > think. Well, it would be great if someone could convert the LilyPond mode of Emacs so that it uses the new 'tree-sitter' interface: https://tree-sitter.github.io/tree-sitter/ (look at the 'Playground' link to get a feeling w

Re: Transparent box around notes

> [...] the snippet is _very_ useful, and certainly much easier to use > than the lsr snippet. Please submit the example as a new LSR snippet. Note that we already have a (slightly different) issue for that: https://gitlab.com/lilypond/lilypond/-/issues/833 It would certainly help if you co

Re: PianoPedalBracket.to-barline doesn't always work as expected

> Might I suggest that “to-barline” is potentially > misleading/confusing…? > > On the other hand: > > end-at-barline, for a pedal coded for release on a note **just > after** a barline, might be more clearly descriptive of the > current behaviour; and > > extend-to-barline, for a

Re: Overriding default text of \f, \p, etc.

> However, trying to define f = #(make-dynamic-script ...) doesn't work > because Lilypond interprets f as a note-name. Try ``` "f" = #(make-dynamic-script ...) ``` Werner

Re: Installing 2.24.1

>> There is a web page that deals with command-line installation, if >> that's what you want: >> >> https://lilypond.org/doc/v2.24/Documentation/learning/command-line-setup >> > Thanks. So basically "yes", I guessed as much. > > I just need to re-associate the new version of lilypond with .ly >

Re: tremoli under beam

Don't you want "\repeat tremolo 2" instead of 4? >> >> Thanks, yes, of course, but the result is still not correct, as >> you've found out. > > Very much not correct! This seems like a bug, no? Let's say it's not supported right now. Filed as https://gitlab.com/lilypond/lilypond/-/iss

Re: tremoli under beam

>>> \repeat tremolo 4 { e32[ c! } >> >> >> Don't you want "\repeat tremolo 2" instead of 4? Thanks, yes, of course, but the result is still not correct, as you've found out. Werner

tremoli under beam

Please have a look at the attached image (from the full score of Stravinsky's Firebird, after rehearsal number 32). How do I correctly notate this in LilyPond? AFAICS, there is no real support for that – at least the 'most natural' way to notate it fails with warnings. I could only manage to wr

Re: a small correction in arithmetic expressions

> Here is a small correction in the documentation which does not affect > the use of Lilypond, just for the sake of correctness of the > formulas... [...] Thanks, this is now part of a merge request, see https://gitlab.com/lilypond/lilypond/-/merge_requests/2291 Werner

Re: nested \set ?

Dear Valentin and Aaron, > properties handle this by having internally not a single value, but > a list of values, and temporary overriding simply means adding to > that list. Context properties do currently not allow for this > mechanic, but we could simulate it ourselves: [...] Both of your

Re: nested \set ?

>> LilyPond provides `\temporary` and `\revert` to set a grob property >> temporarily, and afterwards the value of the grob property is the >> same as before. >> >> Is there a similar possiblity for `\set` (or something usable in >> Scheme)?  I guess not, but I couldn't find this documented >> s

Re: nested \set ?

> > Yes, thanks, but this is not what I'm looking after: At the start > > of my function (created with `define-music-function`), > > `\autoBeamOff` gets called (i.e., the `autoBeaming` context > > variable is set to `##t`), and after the function returns the > > previous value of `autoBeaming` shou

Re: nested \set ?

>> LilyPond provides `\temporary` and `\revert` to set a grob property >> temporarily, and afterwards the value of the grob property is the >> same as before. >> >> Is there a similar possiblity for `\set` (or something usable in >> Scheme)? I guess not, but I couldn't find this documented >> so

nested \set ?

LilyPond provides `\temporary` and `\revert` to set a grob property temporarily, and afterwards the value of the grob property is the same as before. Is there a similar possiblity for `\set` (or something usable in Scheme)? I guess not, but I couldn't find this documented somewhere... Wer

Re: Compress Long Rest in Jianpu.

[Please always reply to the list!] > Sure, it looks like this > [image: image.png] > and this > [image: image.png] > > seems like it just copies the staff style and removes staff lines. OK, thanks. The un-compression of MM rests is an intentional feature of `jianpu10a.ly`. You should contact

Fw: Compress Long Rest in Jianpu.

[Forwarding private message to have the whole conversation in the archive.] --- Begin Message --- Sure, it looks like this [image: image.png] and this [image: image.png] seems like it just copies the staff style and removes staff lines. Windy Werner LEMBERG 于2024年3月24日周日 01:23写道： > &g

Re: Compress Long Rest in Jianpu.

> I want to display both staff and jianpu, but if I enable > \compressMMRests function, the long rests are not compressed when > engraving with jianpu. > > Jianpu support for Lilypond is from file jiapu10a.ly on > https://github.com/nybbs2003/lilypond-Jianpu . Is there any way to > patch the fil

Re: Control breaks in staff that I get from a variable?

>> The classic fix is >> >> << >> \new Devnull { s1*5 \break } >> \staffIGot > > This was exactly what I was after. It’s nice and simple and works > well. Thank you. > > I might wish for it being better documented. I see Devnull > documented well in the Internals Reference, but I didn’t readi

Re: Best way to center beam between upper/lower staff?

> I'm trying to have some notes cross from the lower staff to the > upper staff but want the beam to automatically center. In my > example this is accomplished in measure 3 with much manual work. Is > there a better way? No, there isn't – in general, how shall LilyPond know which note belongs t

Re: Using old definition of bass figures for 6\\, 7\\, 9\\ ...

> adapted sample from > https://lilypond.org/doc/v2.24/Documentation/bd/lily-a6a3b6ba.ly: > > \paper{ > #(define fonts > (set-global-fonts > #:music "paganini" > )) > } > \figures { > \set figuredBassPlusDirection = #RIGHT > <7\\ 6 4 2\+> <4\+ _-> <3 5\+ 3 > <6\\ 4 3> <9\\>

Re: Using old definition of bass figures for 6\\, 7\\, 9\\ ...

> The special font figures introduced with 2.24 breaks old typesets > using fonts provided by https://github.com/OpenLilyPondFonts > > Is there a way to switch to the old behaviour? Please provide a (small, working) example of the problem you encounter. Werner

Re: tied sharps after line break

> 2. LilyPond's default behaviour in this situation is (in my opinion) > sub-optimal. It's a bug known since 15 years... https://gitlab.com/lilypond/lilypond/-/issues/649 Werner

Re: Make D.S. and Coda objects RED

> I found how to color certain objects, such as with: > > \override Staff.TimeSignature.color = #(rgb-color 1 0 0) > > but I have yet to find the names of the objects I'm hoping to change. Have a look at https://lilypond.org/doc/v2.25/Documentation/ly-examples/visualindex.pdf Werner

Re: bookOutputName seems broken in 2.25.12

> I've tried both of the methods of naming an output file in the book > environment. \bookOutputSuffix works fine. Please give complete examples – I can't reproduce the issue (with current git). I've tried ``` \book { \bookOutputName "Comin-Home-Baby_Tenor-1" { c'4 } } ``` and ``` \book

Re: slur to middle of triplet causes warning

> I am trying to slur to the middle of a triplet, which engraves > correclty , but gives a warning. I'd like to get rid of the warning > for a clean build. > > Any solution? > >(e4 d e d | > \tuplet 3/2 {e8 d) b~} b4 r2 | Wrong syntax: Not `(e4` but `e4(`. Werner

Re: Incipit with default noteheads possible?

>> This works for the note heads, but if there happen to be >> accidentals around (in my project this is the case), they remain >> mensural style. Is there another override for this, too? > > How about this? Nice! David, what do you think about converting this code into a proper MR? Wern

Re: Footnote separator line

>> Simply removing \fill-line will shift the line to the left margin, >> leaving the length the same. > > To my eye that looks a lot better. It's really a matter of style. For example, https://tex.stackexchange.com/questions/214644/how-to-add-a-footnote-separator-rule shows a footnote rule exac

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

Re: { } not sounding right.

> I have a branch (from a few years ago) where I changed LilyPond's MIDI > microtonality from using Pitch Bends (which is a bad idea when using > chords) to using MIDI 1.0 tuning information. This works fine IIRC as > long as you don't construct chords containing really close notes > (e.g. c and

Re: { } not sounding right.

> Try this with and without the \new Voice commented. > > \version "2.25.12" > > \language "english" > > \score { > %\new Voice > << > {bf bqf bf} > {g gqs g} > >> > \layout {} > \midi {} > } > > Obviously you would need to listen to the MIDI output. This is a limitation of MID

Re: Setting the emoji font

> I want to use emoji within markup, and I can see in the output log > that Lilypond can't find a character in its default emoji font > (Symbola). I can't figure out how to override the default font. LilyPond does *not* have a default emoji font! It is Pango and FontConfig which choose the font.

Re: Tempo marking doesn't avoid cross-staff slur

>> This issue belongs into the group of the many cross-staff problems. >> AFAICS, we don't have this particular case covered, so please file >> an issue in the LilyPond tracker. > > For reference, it's : https://gitlab.com/lilypond/lilypond/-/issues/6688 Thanks! Werner

Re: Tempo marking doesn't avoid cross-staff slur

> I found a weird behavior -- I don't know if it's worthy of an issue > or not, but here it is: > > The tempo marking will not avoid a slur that goes from staff to > staff. Here is a snippet that shows the problem, and I've attached > an image of it: [...] This issue belongs into the group of

Re: Question about \include options

> It's true that special characters can cause inconsistent results in > almost anything but if you're searching Documentation for a command > that includes them, you expect the search to be 'complete'; i.e., > encompassing all possibities. The thing is that `#f` and `#t` are nothing special; the

Re: Question about \include options

> See for example http://lilypond.org/notation.html, which you reach > by clicking on "details of Notation" at > http://lilypond.org/manuals.html. Could anyone please come up with > a better formulation than "details of ...", since it's far from > intuitive what such a link might contain. Perha

Re: how to install lilypond version on linux (ubuntu 22.04)

> I managed to build a specific stable lilypond version for my linux > distro (Ubuntu 22.04). Because I can not find the wright > documentation on this subject, I like to know how can I install the > generated build files from my build directory on my linux distro. > When I try to install my buil

Re: Collision between accidental and tuplet

> while typing down the score from an old scan, I discovered a > collision between an accidental and a tuplet spanner, or rather the > number in it: > > > \version "2.24" > \language "deutsch" > > \relative c' { > \tupletUp > \times 2/3 { g'=''8 b4 } des8 h~ h4 r4 > } > > > Perhaps this is wo

Re: Cascade Chords

> Is there a special notation for cascade chords (chords played by > adding successive notes )? I could do it by adding a new voice for > each note, but that seems unwieldly and cluttered. https://lsr.di.unimi.it/LSR/Item?id=408 Werner

Re: Forcing custodes to be always placed at the right-hand margin?

> I wanted a more natural text spacing for some chant in modern > notation I am typesetting, using the setting *ragged-right = ##t*. > However, the custodes also moves along with the line, and I would > like it to always be in the same place, at the right-hand margin. > That is, custodes is alway

Re: horizontal spacing issue with `keyCancellation`

Some days ago I wrote: > Consider this snippet. > > ```tex > cancellationFirst = > \override Score.BreakAlignment.break-align-orders = > #(grob-transformer 'break-align-orders > (lambda (grob orig) >(let ((vec (vector-copy orig)) >

Re: Automatically adding extender lines in lyrics

> Often, multiple voices in a score have the same lyrics, or the > lyrics have repeating components (such as lines from a poem). Is > there a way to automatically add extender lines to melismata in the > lyrics? Examples, please, both a scan from a real-world example, and ideally some LilyPond

Re: clefs, time signatures, and key signatures

> does the new proposed spacing mean that the time signatures are not > aligned across staves any more but were before? No, they are aligned as before. Werner

Re: right indent once, horizontal space

> Thank you, yes this works if the measure is the last one. For > exemple in your exemple, I’d need the second staff to have a right > indent. Simply split your music into two scores. You can adjust the distance between the last line of a score and the first line of the next score with the pape

Re: right indent once, horizontal space

> is it possible to add after a bar and before a break some horizontal > space only for a particular system ? Try the `ragged-last` paper variable. Example: ``` \score { { \repeat unfold 60 c'4 } \layout { ragged-last = ##t } } \score { { \repeat unfold 60 d'4 } \layout { rag

horizontal spacing issue with `keyCancellation`

Consider this snippet. ```tex cancellationFirst = \override Score.BreakAlignment.break-align-orders = #(grob-transformer 'break-align-orders (lambda (grob orig) (let ((vec (vector-copy orig)) (middle '(key-cancellation

Re: Why has `NonMusicalPaperColumn` a width?

>> Why does the `NonMusicalPaperColumn` grob have a width of 0.5 >> units? Where it is defined? > > Are you referring to the blue arrow from the second-to-last > non-musical column to the last rest? That's not a width, it's the > [ideal] distance to the last rest's musical column. Yes, it was

Re: clefs, time signatures, and key signatures

>>> please have a look at Merge Request 2188 and comment there on how >>> to proceed with the new distances between clefs and time >>> signatures, together with the new distances between clefs and key >>> signatures. >>> >>> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 >>> >>> The

Why has `NonMusicalPaperColumn` a width?

Consider this example ```tex \version "2.19.2" music = { r4 r r \mark III r } { \music } { \override Score.RehearsalMark.non-musical = #'() \music } \layout { \context { \Score \override NonMusicalPaperColumn.stencil = #ly:paper-column::print \override PaperColumn.stencil = #l

Re: displaying `script-priority`

>> > How can I make LilyPond display the actual values of >> > `script-priority` for a stack of grobs? [...] >> >> Any suggestions how to do that? Otherwise I'll file an issue. > > A few days ago I was looking for something, and stumbled across > https://lsr.di.unimi.it/LSR/Item?id=1017 And I

Re: displaying `script-priority`

Walking through some unanswered e-mails of mine I stumbled across this one, asked in October. https://lists.gnu.org/archive/html/lilypond-user/2023-10/msg00222.html > How can I make LilyPond display the actual values of > `script-priority` for a stack of grobs? [...] Any suggestions how to

Re: lilypond "preprocessor"?

>> One thing occurred to me.  If the original \score did not have a >> \midi block, would it be possible to ask lilypond to produce midi >> output without modifying the input file? > > No, this is not currently possible, although it would be a nice > addition. Stefano, please file an issue for t

Re: clefs, time signatures, and key signatures

> I’ve just looked at the images and especially w/r to the Alto clef I > strongly prefer the new spacing. For the others there are spots > where I’m not sure it is too tight but overall the new spacing > appears to be more balanced. > > I thus think the new spacing is better overall. Thanks, bu

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, together with the new distances between clefs and key >> signatures. >> >> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 >> >> The quest

Re: accessing current file name in markup function

>> The name "sip" is a bit weird; looking in the commit that added the >> code 19 years ago, it looks like it was meant as "smob input" >> (where smob = Scheme object = LilyPond C++ object made available to >> Scheme). Quickly written documentation by an insider. It should be eventually replaced

Re: accessing current file name in markup function

>> Thanks! However, Jean's statement >> >> > markups don't store location info, unfortunately. >> >> is still true, which means that you can't access the current input >> location within `define-markup-command`. > > Yes, sure, but you could inject this during parsing. [...] I'm doing very simila

Re: accessing current file name in markup function

>> Maybe a bit less esoteric: > > Or even less esoteric: Thanks! However, Jean's statement > markups don't store location info, unfortunately. is still true, which means that you can't access the current input location within `define-markup-command`. Werner

Re: accessing current file name in markup function

>> How can I access the current LilyPond input file name from within a >> markup command?  Or do I have to use the (undocumented) >> `delay-stencil-evaluation` functionality? > > If you mean the name of the file from which the command is called > (vs. defined), you can't — markups don't store loc

accessing current file name in markup function

How can I access the current LilyPond input file name from within a markup command? Or do I have to use the (undocumented) `delay-stencil-evaluation` functionality? Werner

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, [...] > > FWIW, I think the Petrucci clef distances are a big improvement and > make incipits closer to what they usually look like in sources. Yes, th

Re: clefs, time signatures, and key signatures

> please have a look at Merge Request 2188 and comment there on how to > proceed with the new distances between clefs and time signatures, > together with the new distances between clefs and key signatures. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 > > The question is whe

clefs, time signatures, and key signatures

Folks, please have a look at Merge Request 2188 and comment there on how to proceed with the new distances between clefs and time signatures, together with the new distances between clefs and key signatures. https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 The question is whether

strange `break-align-symbols` behaviour

Please consider this example. ```tex \version "2.25.11" music = { c'1 \tempo "T-note" c'1 } \markup { time-signature } { \override Score.MetronomeMark.break-align-symbols = #'(time-signature) \music } \markup { time-signature, key-signature } { \override Score.MetronomeMark.break

Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

> Installed 2.24.3 -docs using Macports, No, you didn't. In the very first line of your log file I can see '2.24.2'. The problem vanishes if you *really* install version 2.24.3 – or if you fix up your system setup so that the correct LilyPond version gets found. Werner

Re: Articulate has trouble with grace note at time signature change

>> Please check the looong list of bugs related to `\articulate` >> whether it has already been reported. > > Seems to be #3696, reported - by you - in 2013. D'oh :-) Werner

Re: Articulate has trouble with grace note at time signature change

> This fails in 2.24.1 with messages about mid-measure time signature > change and failed barcheck: > > \include "articulate.ly" > \articulate > { > \time 4/4 > c'1 | > \time 3/2 > \grace d'8 c'1. | > } > > Succeeds if \articulate is not used. I can work around it by > tagging MIDI and

Re: Mensural Lines in Choir Staff

Omit the 'Staff.' within '\context \Staff'    Werner 20.11.2023 11:04:24 Johannes Roeßler : > Am 17.11.2023 um 20:11 schrieb Shane Brandes: >> \override Staff.BarLine.transparent = ##t > > Hi Shane, > > maybe I use the wrong place, but this doesn't work for me: > > \version "2.24.0" > > \lay

Re: top-level `\midi` doesn't work as expected

> Would it be possible to reformulate a bit to make it even more clear > that this is analogous to how \layout blocks behave (the only > difference being that a \score block that contains nor a layout > neither a midi block implicitly contains a layout block). For > example: [...] Sorry for th

Re: top-level `\midi` doesn't work as expected

> MIDI settings can be changed globally (or in a book or bookpart), but > the generation of an actual MIDI file is only triggered when a \midi > block is encountered inside of a \score . Thanks for the idea and wording. https://gitlab.com/lilypond/lilypond/-/merge_requests/2171 Werner

Re: top-level `\midi` doesn't work as expected

> Thanks. I'll add this information to the NR. > > > Right now, the NR says the following > (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html). > What > do you think needs to be clarified? > > To create a MIDI output file from a LilyPond input file, insert > a\mid

Re: top-level `\midi` doesn't work as expected

>> I wonder whether it is expected that this simple input >> >> ``` >> { c' } >> \midi{} >> ``` >> >> doesn't create a MIDI file. > > > Yes. [...] Thanks. I'll add this information to the NR. Werner

top-level `\midi` doesn't work as expected

[2.24.2, 2.25.10] I wonder whether it is expected that this simple input ``` { c' } \midi{} ``` doesn't create a MIDI file. I have to explicitly put everything into a `\score` block to get that. For me, this looks odd, and I couldn't find a hint in the documentation for that behaviour.

Re: Questions about LSR

> I have some questions about the LSR and I hope this is the place to ask > them. > > I have noticed that some snippets take up a lot of blank space under > them. This is because they have marked the snippet as stand-alone, > but haven't put a "tagline = ##f" in the paper or header block. I'm

Re: Switching between one staff and two

>> https://lilypond.org/doc/v2.24/Documentation/notation/modifying-single-staves#hiding-staves > > Thanks. I've been playing around with this, but I still am not sure > how to make it work -- I've tried a few things, and it's not > removing the empty staves. OK. Please construct an example how

Re: zero horizontal space between note heads

> But the NoteColumn is slightly wider than the NoteHead. Ah, thanks. The question is: Why? Where does this additional 'padding' come from? I searched again the IR for an answer but couldn't find something relevant. > If you show the NoteColumn skylines, and set packed-spacing == ##t, > you

Re: zero horizontal space between note heads

>> If I set `packed_spacing`, it's getting a little bit tighter, but >> there is still horizontal whitespace between the note heads, and I >> still don't know where it comes from. > > What happens if you set the Beam X-extent to point-stencil (or > whatever)? Alas, this doesn't help. Replacing

Re: zero horizontal space between note heads

> [...] However, there is still some horizontal space between the note > heads. What is it? I tried hard to find something in the IR but > wasn't successful... If I set `packed_spacing`, it's getting a little bit tighter, but there is still horizontal whitespace between the note heads, and I st

zero horizontal space between note heads

For testing purposes I try to eliminate spacing completely. I tried ``` \version "2.25.9" #(set-global-staff-size 26) { \override Staff.Clef.show-horizontal-skylines = ##t \override Staff.KeySignature.show-horizontal-skylines = ##t \override Staff.TimeSignature.show-horizontal-skylines =

Re: Switching between one staff and two

> I've pasted some example code after my signature I'm having trouble with. > Can anyone help me solve these problems: [...] Look up the documentation of `Keep_alive_together_engraver`, which explains how to make LilyPond split such divisi parts automatically. https://lilypond.org/doc/v2.24/Doc

Re: Formatting for a tie

> How can I format this tie in Lilypond? I'm writing a Lilypond file > for an existing song; this image is from a scan of a hymnal. ``` { << { a'8[( g']) } \\ { e'4 } >> } ``` Werner

Re: Clipping of ornamentation glyphs

> I just noticed something with both that version of the documentation > as well as 2.25 [1]. The curl of the "up" or "down" is getting > clipped at the top and bottom of the ornamentation snippets. > However, "line" seems to be intact. Are the bounds of these curl > glyphs not being calculated

displaying `script-priority`

How can I make LilyPond display the actual values of `script-priority` for a stack of grobs? Let's assume I have ``` { \set strokeFingerOrientations = #'(up) \set fingeringOrientations = #'(up) } ``` and I want to position the fingerings for the upper note above the fingerings of the lo

Re: Tuplet brackets too short?

> Shouldn't both tuplet brackets span every notecolumn within the > purview of the last note's duration? Yes, at least according to Gould. Using `tupletFullLength` helps, but now tuplet brackets are too long: ``` \new Staff { \set Staff.tupletFullLength = ##t \time 2/4 << \tuplet 3/2 { c''4

Re: Still failing to operate lilypond 2.20.0 64-bit version.

> From the attached photo you will see that I created in 'home' a > folder called 'LilyPondArea', and in that a folder called > 'lilypond-2.24.2'. In the former I placed the downloaded tar, and in > the latter the unpacked files of lilypond-2.24.2 (i.e. 'bin', etc) Looks good. > I use Textedit t

Re: Where is my tuplet bracket?

> \new Staff { > \key c \minor > < es' g' > < bes' d''~ >2. | > \tuplet 3/2 \voices "",2 << { \voiceOne d''4 c'' es'' \oneVoice } \\ > { g'4 as'2 } >> > < f' as' >4 | > } Looks like a bug, so please file a report. Werner

Re: adding accidental to "tr" for trill spanner

>> Have you looked at >> http://lilypond.org/doc/v2.25/Documentation/notation/trills ? >> > Many times. If you can't find something in the docs, you should try the LilyPond Snippet Repository next: https://lsr.di.unimi.it Entering 'trill' into the search box you will soon find https://lsr

Re: how to modify footnote numbered mark line length

> Here is the example. The line between the grob and the footnote number is controlled by the number's position, i.e., the first argument to the `\footnote` command. ``` \version "2.24.2" { \footnote #'(-1 . 3) "A note." a'4 a'4 \footnote #'(-5 . -5) "Another note." a'4 a'4 } ```

Re: how to modify footnote numbered mark line length

> someone know how to modify line length footnote between number and > music object? Please show images that explain what you want to do. Werner

Re: New version 2.25.9 on Windows "feels" slower and less reliable

> The attached file is pretty much as minimal as I can reduce > it. Removing more bars makes it compile w/o error. Thanks. As it turns out, this has already been reported: https://gitlab.com/lilypond/lilypond/-/issues/6175 I've added your sample. Werner

Re: New version 2.25.9 on Windows "feels" slower and less reliable

>> Assertion failed: my_index == 0, [...] > > I found what triggered this Assertion: > In my file I had a > \new Lyrics ... > outside of any Staff or Score context. Please provide a minimal example that so that we can add an issue to the tracker. Werner

Re: Still failing to operate lilypond 2.20.0 64-bit version.

>> I think it's ghostscript – there are no pre-built packages >> available either. While LilyPond doesn't link to it in normal >> builds, gs is needed for converting LilyPond's EPS output files to >> PDF. In other words, a MacPorts user still needs a compiler... > > Damn, you are right. libpape

Re: Still failing to operate lilypond 2.20.0 64-bit version.

>> Ah, now I remember, thanks! I wasn't fluent enough then with the >> 'ports' program to find out which of the dependencies actually uses >> libpaper, since LilyPond itself [doesn't use it]( >> https://github.com/macports/macports-ports/blob/master/textproc/lilypond/Portfile >> ) > > It's most

Re: Still failing to operate lilypond 2.20.0 64-bit version.

> Ah, now I remember, thanks! I wasn't fluent enough then with the > 'ports' program to find out which of the dependencies actually uses > libpaper, since LilyPond itself [doesn't use > it](https://github.com/macports/macports-ports/blob/master/textproc/lilypond/Portfile) I've even asked to swit

Re: Still failing to operate lilypond 2.20.0 64-bit version.

> It's in the non-distributable list: > > not-distributable.txt:lilypond "lilypond" is not distributable > because its license "GPL-3+" conflicts with license "GPL-2" of > dependency "libpaper" not-distributable.txt:lilypond-devel > "lilypond-devel" is not distributable because its license "GPL-

Re: Lyrics above staff

>>> Le 6 oct. 2023 à 15:47, David Kastrup a écrit : >>> \new Staff = "staff" { >>> c'1 >>> } \addlyrics \with { alignAboveContext = "staff"} { Om } >> >> >> OMG! I didn't know that syntax at all. It looks undocumented. > > Sigh. We definite

Re: Still failing to operate lilypond 2.20.0 64-bit version.

>> Again: license issues, as far as I know (but not from Apple in this >> case). > > Are you sure? It seems to me that it just wants clang from XCode. > I can't imagine what else could be useful for building LilyPond and > provided by XCode. Well, there are no pre-built 'lilypond' (or 'lilypond

Re: Still failing to operate lilypond 2.20.0 64-bit version.

> You are very kind. I shall give it a go. But I think you will have > to agree that this is some 5 orders (***) of magnitude more complex > than versions: 2.12.3, 2.18.2-1, and 2.20.0. I never would have got > into Lilypond were I starting from here. Please always bear in mind that *none* of t

<    1   2   3   4   5   6   7   8   9   10   >