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

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

David, > Perhaps that might be made clearer in the macOS section of > https://lilypond.org/doc/v2.25/Documentation/web/download . Could you provide better wording for this and the other issues you are mentioning? I can then incorporate your changes into the documentation. Werner

Re: vertical spacing of top-level `\markup` and `\bookpart`

>> If I activate the `\bookpart` block, the stretchability is >> completely lost – both inside and outside of `\bookpart`. Is this >> expected? How can I control the stretchability for global markups >> section-wise (e.g., in `\bookparts`)? > > If you add ragged-last-bottom = ##f in your \paper

vertical spacing of top-level `\markup` and `\bookpart`

Consider this example. ``` \paper { markup-markup-spacing.stretchability = 1000 tagline = ##f } \markup "top" \markup "middle" \markup "bottom" \pageBreak %\bookpart { { c' } \markup "top" \markup "middle" \markup "bottom" %} ``` If I activate the `\bookpart` block, the stretchab

Re: `\paper`-only variables

>> I'm working on issue >> https://gitlab.com/lilypond/lilypond/-/issues/1392 (but not for the IR >> but as an appendix for the NR) and I would like to avoid writing the >> sentence >> >> `foo` may also be specified in `\layout` blocks >> >> again and again. I could imagine that the opposite, n

Re: `\paper`-only variables

>> Do we have a list of variables that only have an effect if set in >> `\paper` (and not in `\layout`)? > > What do you want this for? I'm working on issue https://gitlab.com/lilypond/lilypond/-/issues/1392 (but not for the IR but as an appendix for the NR) and I would like to avoid writing th

`\paper`-only variables

Do we have a list of variables that only have an effect if set in `\paper` (and not in `\layout`)? Werner

Re: lilypond 'not recognized'

> Thank you Jean for pointing me to those instructions. They are very > clear. I followed them to the letter. I used plain cmd -- even in > admin mode -- and edited the path to where my LilyPond 'bin' is > located. I closed/re-opened cmd. I even restarted the computer. I > still get the same

'festival' support, 'lilysong'

Folks, is anybody using the 'festival' support files that come with LilyPond? Or maybe the 'lilysong' script? If you do, please write back! Werner

Re: shifting accidentals horizontally

> A possible solution for this could be to do a similar thing to add > certain note columns to separate NoteCollision grobs, so they can be > spaced independently. I've added Valentin's solution as a new snippet to the LSR. https://lsr.di.unimi.it/LSR/Item?u=1&id=1172 Werner

LilyPond Visual Index

Folks, I've just submitted a Merge Request for a new version of the LilyPond Visual Index, to be added to LilyPond's documentation. https://gitlab.com/lilypond/lilypond/-/merge_requests/2107 Please comment! Werner

Re: tagline = ##f does not work in score header block

> Another observation: tagline is not in either the command index or > the index in the Notation Manual. The documentation I could find on > tagline was pretty sparse (unless I missed something). I've added index entries in https://gitlab.com/lilypond/lilypond/-/merge_requests/2104 Wer

Re: tagline = ##f does not work in score header block

> Suppose tagline "worked" in \score blocks. What would this code print? > > \version "2.24.2" > > \score { > \header { > tagline = "Tagline 1" > } > { c' } > } > > \score { > \header { > tagline = "Tagline 2" > } > { d' } > } > > \score { > \header { > tagline = "Tagline

Re: Custom custos pitch

> Do you know how to trick the custodis stencil calculation to be set > a given pitch? I will extract the first NoteEvent from the ligature > – that's not a problem. I don't know how to make this custos appear > at the desired position. Maybe the thread starting with https://lists.gnu.org/ar

Re: Controlling slur shapes automatically

>> I've solved it differently, see >> >>   https://gitlab.com/lilypond/lilypond/-/merge_requests/2103 >> >> 'All layout objects' is better suited as a reference than 'Graphical >> Object Interfaces' IMHO. > > Why? In this instance, you can see that you need to look into > slur-interface, not jus

Re: Controlling slur shapes automatically

>>> I have a feeling that I could do a lot with the Slur.details >>> alist, but the function of the symbol/value pairs is not always >>> clear. Is there documentation on these? >> >> >> Each details value is documented on >> >> https://lilypond.org/doc/v2.24/Documentation/internals/slur_002dinterf

Re: automatic accidentals in subsequent measure(s) of *a different staff* in a PianoStaff context

> %% An accidental style that also prints cancellation signs in the > %% following measure for different octaves ("piano" only does it for > %% the same octave). Nice! Shall we add this to LilyPond proper? Werner

Re: \pitchedTrill not displayed

> I don't get the musical meaning of having two simultaneous trills > *in the same voice* (as opposed to simultaneous trills in two > different voices). Irrespective of the current issue, having a trill on a chord, with all notes involved, is happening regularly in piano music. Attached is an ex

Re: Font problem on Mac

> Jean did the analysis then, he can tell more. D'oh, *I* did the analysis then :-) https://gitlab.com/lilypond/lilypond/-/issues/6508 Werner

Re: Font problem on Mac

>>> I do not think that my Times New Roman font is corrupted. > > Actually, I think it is: Most likely the font's 'post' table is > broken (i.e., it has a wrong PostScript name for glyph 'N'). > Normally, you won't see the problem at all because most applications > access a font's 'cmap' table (

Re: Font problem on Mac

>> I am experiencing a very weird problem with Lilypond on macOS 13 >> Ventura. When using the Times New Roman font, the capital letter N >> is mis-printed. Have a look at the thread starting at https://lists.gnu.org/archive/html/lilypond-user/2022-12/msg00349.html which discusses a very s

Re: Using a custom bitmap as a character?

> I am slowly creating a font to be used for tablature ... so far I > have bitmaps of a couple of characters. I'd like to try them out > and get an idea how they look. Is there any way I can replace a > character with a small scaled bitmap? Not directly. You would have to convert the bitmap t

Re: "Slash" in figured bass

>> In particular, there is no fitting glyph in the SMuFL specification >> (AFAICS). Consequently, a simple `\markup` solution is probably >> the way to go. > > The slash is pronounced the best of several possibilites by > C. Ph. E. Bach [...] Thanks. Please open an issue for SMuFL at https

Re: "Slash" in figured bass

> From Förster's book: > https://www.digitale-sammlungen.de/view/bsb10527178?page=64 ex. 141 > I also attach an example from his "Practische Beyspiele", in which a > slightly different layout is being used in which the slash and the > figure are put separately over their respective notes. > > Of

Re: Suggestion: Hooks for formatting titling fields

> In my opinion it would not affect the complexity of Lilypond much to > add such hooks to all common markup fields, and it would make > tweaking specific fields much easier. I like your idea, thanks! What about preparing a MR so that everything is formalized? I can imagine that your idea (hav

Re: Staggered/Tabled display

> I am trying to look into if a particular layout is possible with > Lilypond. I'd like to display small groups of short musical examples > as a "table", or "staggered". I'm not sure what to call it so I've > attached a photoshopped markup of what I am trying to achieve. > > I'd like to display i

Re: spacing

>> It depends on the hyphenation rules (i.e., either UK or US >> english). [...] > > Hyphenation rules or not, for _singing_ purposes it tends to lead to > better perfomances to put consonant groups at the start of the next > syllable rather than the end of the current one. Gould in general disa

Re: spacing

> are you sure "theology" should go "the - ol - o - gy"? Shouln’t it > be "The - o - lo - gy"? It depends on the hyphenation rules (i.e., either UK or US english). Have a look at https://www.merriam-webster.com/dictionary/theology to see the former as used in the US. Werner

Re: QUIBBLE: Interesting use (mis-matched) of left and right quotes of quoted strings in Lilypond output

> QUIBBLE: Interesting use (mis-matched) of left and right quotes of > quoted strings in Lilypond output > > Processing `Were_You_There.ly'... [...] As others mentioned already, this is deliberate. It was the standard GNU quoting style many years ago, and it looked OK then with most fonts, bo

Re: cross-staff stems

In March we had the following discussion about cross-staff stems. > The documentation does not explicitly relate stem direction with > location of command. So I am very fortunate to have your > expertise. Can you please suggest a better wording that I can add to the d

Re: broken slurs shorter than ties

>> Suprisingly, no – at least I couldn't find an entry.  I've now created >> >> https://gitlab.com/lilypond/lilypond/-/issues/6631 > > And there is now https://gitlab.com/lilypond/lilypond/-/merge_requests/2043 > > See, if you report problems, there is a chance they actually get > fixed :-) Wi

Re: broken slurs shorter than ties

> Cough, cough. I have found this to work: > > ``` > \version "2.25.5" > > #(set-default-paper-size "a6") > > { > d'4 e' g' d' | > d'4 e' g' d'( ~ | > \once \override Staff.KeySignature.break-visibility = #all-invisible > \break > d'4) e' f' d' | > d'4 e' f' d' | > } > ``` Very int

broken slurs shorter than ties

In my opinion, the worst flaw of LilyPond's otherwise excellent formatting, a flaw that essentially everyone encounters rather quickly, is that broken slurs are almost always shorter than broken ties (it should be exactly the opposite), which is butt ugly and sometimes really hampers readability.

Re: shifting accidentals horizontally

> A possible solution for this could be to do a similar thing to add > certain note columns to separate NoteCollision grobs, so they can be > spaced independently. However, it your case it should suffice to > prevent any Collisions to be detected by doing > > \once\override Staff.NoteCollision.n

Re: shifting accidentals horizontally

> @Werner I’ve added a small fix concerning the case when there is no > NoteCollision grob (in which case this should not be relevant in the > first place). Thanks a lot! I think this would be a great snippet for the LSR. Note, however, that there are alignment problems with other staves, see b

Re: shifting accidentals horizontally

> Even though I can imagine this happening, I don't recall seeing it > as a pianist. Even if you tweak it to swap the note columns, I > think it will still be a bit confusing. As Damian has observed, there are plenty of examples in Bartók's piano sonata. Other, similar situations can be found i

Re: shifting accidentals horizontally

> Not the answer to the Lilypond question, but as a reference of > comparison, here is what Dorico does in this situation by default, > and I believe this to be correct standard practice. Well, it can't be generalized – sometimes LilyPond's default is the right choice. However, it would be nice

shifting accidentals horizontally

Please consider the example code below. The first line shows LilyPond's default, the second line shows what I need. As can be seen, the solution in the second line is imperfect – I just did the most basic changes to demonstrate what I want, namely the down-stemmed note to be positioned after the

Re: MEI to MusicXML

>> Thanks for the link(s) to this repository, and sorry for the very >> late reply. I'm going to try >> >> https://github.com/cemfi/meico >> >> which uses the 'music-encoding' XLST stylesheets, AFAIK, and, >> according to the release news (from last week) is now able to read >> and write Music

Re: Magnetic snap and whiteout on LyricText: warnings

> [...] I submitted the snippet to LSR as no. 1169 (pending approval) > in the attached form. Thanks! Werner

Re: Time signature cancellation

> It's not unusual, just not Common Era period which lilypond > principally focuses on. Understood. However, we *need* good real-world examples that are not bound to certain notation programs so that we have a chance to find a generic implementation. > One example has been given. Do you need m

Re: Time signature cancellation

> you just want a recent real-world example? Birtwistle: Harrison’s > Clocks. Thanks! Werner

Re: Time signature cancellation

>> Has anyone here ever used or seen the X-shaped time-signature >> cancellation sign pictured at [1], or anything similar? > > It's one standard for open meter. > > Here's the Dorico manual info: [...] Thanks, but ideally we would like to see a real-world example that predates recent notation pro

Re: Embed files other than source code in PDF file?

>> I have been using the line >> >> #(ly:set-option 'embed-source-code #t) >> >> to embed the lilypond files I used in the PDF, but was wondering >> if there was a procedure I could call to embed some other file, >> such as a PDF of the source I used for the transcription? Sorry,

Re: MEI to MusicXML

Hello Jean and Silvain, >> for a blind student of mine I would like to convert MEI files from >> the Digital Mozart Edition >> >> https://dme.mozarteum.at/movi/en >> >> to MusicXML, which he can convert to something readable on his >> Braille terminal. >> >> Any idea how to do that? > > Apparen

Re: reducing gap between vertical volta lines

> Perhaps a new property for `VoltaBracket` is needed, say, > `edge-distance`: > > * If set to `#f`, position the right vertical line of the left volta > bracket at the left side of the barline (which is the default > behaviour right now). > > * If set to a numeric value, it specifies the dist

clef and volta issues

Consider this example. ``` { c'1 | \repeat volta 2 { c'1 \clef bass | \alternative { \volta 1 { c1 \clef treble | } \volta 2 { \clef bass c | } } } } ``` There should be a change treble clef right before the repeat barline, and there shou

Re: reducing gap between vertical volta lines

>> As the attached image shows (Henle, Beethoven's violin sonatas >> vol. 1), the vertical lines of the volta repeat are very near, much >> nearer than what LilyPond produces by default. What is the best >> way to achieve this layout? > > Is `shorten-pair` enough for you? > > ``` > \version "2.

reducing gap between vertical volta lines

As the attached image shows (Henle, Beethoven's violin sonatas vol. 1), the vertical lines of the volta repeat are very near, much nearer than what LilyPond produces by default. What is the best way to achieve this layout? Werner

Re: Need help using math in markup command definition, and a feature request.

>> >> D'oh, this should be >> >> ``` >> (define (foo bar) >>   (define (baz) >>     ... >>     (if bar)    ; Is 'bar' visible here?  If yes, when is >>   ...   ; 'bar' expanded?  At the time 'baz' is >>     ; defined? At the time 'baz' is executed? >> ``` > > I do

Re: Need help using math in markup command definition, and a feature request.

> BTW, I suggest to cover one more issue with local variables, namely > whether arguments to a function are seen in sub-functions, which are > IMHO a very good addition to `let` and `let*` to write clean and > readable code – often much more readable than anonymous lambda > expressions. > > Examp

Re: Need help using math in markup command definition, and a feature request.

> Second, you need to use `let` here, not `define`. See > > https://extending-lilypond.gitlab.io/en/scheme/local-variables.html BTW, I suggest to cover one more issue with local variables, namely whether arguments to a function are seen in sub-functions, which are IMHO a very good addition to `l

Re: How can I print only some parts of a score (staves, but no chords)?

> Sure! Just > > \include “chorded.ily” Just to avoid potential problems: This must be \include "chorded.ily" i.e., straight doublequotes. Werner

Re: Compilation errors 2.24.1 Fedora 38

>> Alas, LilyPond doesn't support it for technical reasons. > > They work just fine in the Cairo backend though. Andrew, try > compiling with the `-dbackend=cairo` option. This currently fails with variation fonts based on CFF2 technology, like 'Noto CJK VF'. Apparently, LilyPond tries to emb

Re: Compilation errors 2.24.1 Fedora 38

> > > warning: font index 262144 too large for font > > > `/usr/share/fonts/google-noto-vf/NotoSans[wght].ttf', using index 0 > > > > This is a variation font, which LilyPond doesn't support. I > > suggest that you explicitly specify the font in your `.ly` file > > that you are going to use. htt

Re: Compilation errors 2.24.1 Fedora 38

> With 2.24.1 on Fedora 28 I am getting two issues with one file. > > > 1. = > > warning: font index 262144 too large for font > `/usr/share/fonts/google-noto-vf/NotoSans[wght].ttf', using index 0 This is a variation font, which LilyPond doesn't support. I suggest that you explicitly spe

MEI to MusicXML

Folks, for a blind student of mine I would like to convert MEI files from the Digital Mozart Edition https://dme.mozarteum.at/movi/en to MusicXML, which he can convert to something readable on his Braille terminal. Any idea how to do that? Werner

Re: Global fonts

>> \paper { >>   text-font-size = 16 >> } > > I would want to create a better interface for it before documenting > it. For example, right now, it must be put after > set-global-staff-size, and it also can't be different for the sans > or typewriter font. Hmm, maybe using alists that override t

Re: Global fonts

> If you use version 2.25.4, then it's possible to set the size for > text fonts [...] > > \paper { > text-font-size = 16 > } This is great! And completely undocumented. There isn't even a regtest... Werner

Re: Modal notation

> 1. I’m not finding a symbol for a “plica”: single note with >ascending or descending tail on both sides. Does that exist? Yes, see attached image, but there isn't an explicit command to access it. You have to use ligatures; look up the documentation for `\deminutum`. > 2. More seriously:

Re: flageolet is not listed in the index portion of the Notation Reference

> I was searching in the Index for 'flageolet' instead of '\flageolet'. > I global search of 'flageolet' and following every result determined > this. This is an artifact of our ancient `texi2html` version which are we are currently still forced to use. In the PDF manual, the index entries look

Re: Tuplet spacing comparison

>> I happened to be checking tuplet notation in Gould today, and it >> strikes me that the default LilyPond treatment of tuplet brackets >> shown by that example does not follow her clear default rule (which >> is also stated by Ross, and followed without comment by Stone and >> loosely (!) by Rea

Re: "Closed" fret diagrams

> There is something I do not like about the fret diagrams in > Lilypond: > > The diagrams are "open" on the side pointing towards the bridge of > the instrument, with the strings "sticking out" on that side. How > could I achieve closed rectangles in Lilypond like e.g. the > "MusFrets" font doe

Re: converting `\markuplist` to `\markup`

> how should \column not be the "right" way? A markup list is a list > of markups, but does not contain any information about how these > should be positioned. [...] In hindsight everything's clear now, thanks :-) Werner

Re: mensural ligature

>> Pál, can you please comment? It looks as if support for this >> ligature form is missing... > > It's not missing, but it means something else: the duration sequence > 1 1 \longa. > > ``` > \[ a'1 c'' a'\longa \] > ``` Indeed, this gives the right optical result, thanks! > So long I thought

Re: Can't compile LSR #1000 with 2.25.4

>> Any idea how this can be fixed? > > Fixed in LSR (hint: `#(debug-enable 'backtrace)` helps in such > cases). That was fast, thanks! Werner

Can't compile LSR #1000 with 2.25.4

After inserting a version statement and running `convert-ly` on http://lsr.di.unimi.it/LSR/Item?id=1000 I get this ominous error: ``` init.ly:64:2: error: Guile signaled an error for the expression beginning here # (let ((book-handler (if (defined? 'default-toplevel-book-handler) In procedu

Re: mensural ligature

> I try to set this ligature for an incipit: > > > using > > ``` > \version "2.24.0" > > { > \override NoteHead.style = #'mensural > \[ a'1 c'' > \override NoteHead.ligature-flexa = ##f > a'\breve \] > } > > \layout { > \context { > \Voice > \remove "Ligature_bracke

Re: Vertical spacing between wordwrap items within markup column

>> This smells like a bug: `\wordwrap-string` returns a bunch of lines >> spaced by `baseline-skip`, but no such skip is applied after the >> last line, for whatever reason. > > Why would it be applied after the last line? Oh, I didn't mean that `\wordwrap-string` actually should insert such a

Re: Vertical spacing between wordwrap items within markup column

> btw: why is it named "baseline-skip" and not "baseline-distance"? This is historical: LilyPond's origins are with TeX, and a 'skip' in TeX is a stretchable and/or compressable whitespace (either horizontal or vertical).[0] The baseline-to-baseline distance is such a skip in TeX; the correspon

Re: Vertical spacing between wordwrap items within markup column

> Maybe I'm missing something here, but how can I make the space > between items in a markup column regular? As you can see in the > example, if the text is short so that there is no wrapping > necessary, the space is fine. But the "a a a" item does wrap around > and overlaps a bit with the "b b

Re: converting `\markuplist` to `\markup`

> What do you mean by “convert”? Probably bad wording: I mean to wrap a markup list into a markup. > I don’t know what it means to convert a markup list to a markup, > since there are many ways in which you can combine the stencils: > \column, \center-column, \line, \concat, \fill-line, etc. I

converting `\markuplist` to `\markup`

What's the proper way to convert a `\markuplist` to a `\markup`? `lilypond-book` splits a top-level `\table` into separate lines; I want to avoid that because it prevents fine-tuning of the vertical spacing of rows. Right now I do ``` \markup \column { \table ... } ``` Werner

Re: `TextMark` doesn't react to `staff-padding`

>> I expect that both the 'x' and the 'g' are aligned at the baseline. >> However, it doesn't work. >> >> AFAICS, the `TextMark` grob contains `side-position-interface`. What >> am I missing? > > See https://gitlab.com/lilypond/lilypond/-/issues/342 Interesting, thanks! I wouldn't have expec

`TextMark` doesn't react to `staff-padding`

Please have a look at this snippet: ``` { \override Score.TextMark.staff-padding = 2 \textMark "x" c'' \textMark "g" c'' } ``` I expect that both the 'x' and the 'g' are aligned at the baseline. However, it doesn't work. AFAICS, the `TextMark` grob contains `side-position-interface`. Wha

Re: ANN: Frescobaldi 3.3.0

Dear Frescobaldi team, > We are glad to announce the availability of Frescobaldi 3.3.0. > [...] Is it necessary to update the Frescobaldi installation instructions in LilyPond's Learning Manual? https://lilypond.org/doc/v2.25/Documentation/learning/installing https://gitlab.com/lilypond/

Re: movement in markups like TeX's `em` and `ex` units

> Consider the following snippet: > > ``` > Emaj = \markup { E \raise #1 maj } > > \markup \Emaj > > \markup \fontsize #10 \Emaj > ``` > > As can be seen, `\raise #1` is not the right value in the second > case. [...] This is now https://gitlab.com/lilypond/lilypond/-/issues/6576 Wern

movement in markups like TeX's `em` and `ex` units

Consider the following snippet: ``` Emaj = \markup { E \raise #1 maj } \markup \Emaj \markup \fontsize #10 \Emaj ``` As can be seen, `\raise #1` is not the right value in the second case. What I would like to have instead is an equivalent to TeX's relative units `em` and `ex`, being multiples

Re: temporarily overriding paper variables

> [https://gitlab.com/lilypond/lilypond/-/issues/6566](https://gitlab.com/lilypond/lilypond/-/issues/6566) > > I am pretty surprised that this fundamental bug went unnoticed over > the years (not sure for how long it has been around). LilyPond's > page layout is smart, but sometimes I think it's

Re: left margin difference between `\markup` and `\table`

> `\rounded-box` does not displace its argument, it only adds a box > around it. In the first case, the stencil has protrusion on the left > (the start of its horizontal extent is negative). This doesn't > happen in the second case because `\table` realigns everything. Try > > ``` > \markup \lef

left margin difference between `\markup` and `\table`

Consider the following example. ``` \paper { left-margin = 0 } \markup \rounded-box { foo } \markuplist \table #'(-1) { \rounded-box { foo } } ``` Why is there a difference in the formatting? I would like to have the same behaviour – ideally, `\markup` should also take the rounded box int

Re: bookOutputName still gets "-1" suffix added to SVG file names

>> Or am I still missing the one place where that explanation is >> provided? > > It's here: > > https://lilypond.org/doc/v2.24/Documentation/usage/other-programs I've added links. https://gitlab.com/lilypond/lilypond/-/merge_requests/1901 Werner

Re: bookOutputName still gets "-1" suffix added to SVG file names

> Going back to the manuals didn't help explain tall-page-formats: > [...] > > Maybe the documentation of separate- and tall-page-formats > should elaborate more. This is very likely. May I invite you to provide improvements to the text? You have first-hand experience :-) Werner

Re: temporarily overriding paper variables

>> >> Alas, it *still* doesn't work as expected.  Obviously, I have >> >> simplified the code example too much: adding a `ChordNames` context >> >> prevents alignment.  Note that the top skyline of the chord symbol >> >> doesn't show anything suspicious. > > I am not yet sure if this is a bug or n

Re: temporarily overriding paper variables

>> Alas, it *still* doesn't work as expected. Obviously, I have >> simplified the code example too much: adding a `ChordNames` context >> prevents alignment. Note that the top skyline of the chord symbol >> doesn't show anything suspicious. > > Okay, then I think we are hitting something else.

Re: temporarily overriding paper variables

> > \markup \with-dimensions #'(0 . 0) #'(2.5 . 0) > \general-align #Y #UP "foo" > > > The vertical extents #'(0 . -2.5) and #'(2.5 . 0) both have the same > effective height of -2.5 units, however they have a different > relative starting point which is important for what may appear >

Re: insert a `Custos` grob manually

>> [...] the ideal solution would be that the custos is really at the >> end of the staff line, and the extra note is just there to indicate >> at which pitch the custos gets typeset. > > This should do: It does, thanks a lot! Werner

Re: temporarily overriding paper variables

>> It would be cool if this worked some day. However, the next best >> thing would probably be to allow negative widths and heights for >> `\markup` boxes (if set with `\with-dimensions` and friends). > > Was messing about a bit. Does this work on your side? Alas, no. It is probably related t

Re: insert a `Custos` grob manually

>> I would like to have a command that inserts a `Custos` grob.  Note >> that it should really be a `Custos` grob and not something else so >> that `\BalloonGrobText Custos ...` works. >> >> Is there a possibility to do that? > > What is the context? Do you want the custos' pitch to be determined

insert a `Custos` grob manually

I would like to have a command that inserts a `Custos` grob. Note that it should really be a `Custos` grob and not something else so that `\BalloonGrobText Custos ...` works. Is there a possibility to do that? Werner

Re: temporarily overriding paper variables

>> I tried >> >> ``` >> \markup \with-dimensions #empty-interval #empty-interval { >> ... } >> ``` >> >> and the padding to the next score gets still applied. I suspect >> that the 'empty interval' trick only works for stuff within a score >> but not on the top level. > > I'd be tempted to call

Re: temporarily overriding paper variables

>>> If you don't want vertical padding, your horizontal dimensions >>> must be an empty interval, not a point interval. >> >> OK, but how do I do that for `\markup`? > > Maybe this: \markup \with-dimension #X #empty-interval ... > > (Assumes you are using 2.24 that supports the axis-specific

Re: temporarily overriding paper variables

>> ``` >> \markup \with-dimensions #'(0 . 0) #'(0 . 0) { >> ... >> } > > If you don't want vertical padding, your horizontal dimensions must > be an empty interval, not a point interval. OK, but how do I do that for `\markup`? Werner

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