-snippets-*.tar.gz` files don't contain
any additional information not already contained in
`lsr-*.mysqldump.gz`.
Werner
but I never found the time and energy to actually do that...
Werner
> FWIW I have used all of these technologies and would be willing to
> help.
This is great news! I'm very glad to hear that.
Werner
evel/2025-06/msg00032.html
I hope this answers your questions. If not, please don't hesitate to
ask more!
Werner
for the time being (since this is the least amount
of work, we estimate), with various improvements to be done
afterwards.
If you want to be that White Knight, please contact us and Sebastiano!
Werner
> Another question: there's a way to disable the creation of backup
> files ending with ~?
Nope.
Werner
ault convert-ly is updating all the \version strings even if
> there's no syntax change. [...]
>
> Am I missing something?
Yes, you do :-)
-d, --diff-version-update
only update \version number if file is modified
Werner
snippet to avoid the overrides for 'font-name.
> The default-font prints correctly.
> https://lsr.di.unimi.it/LSR/Item?id=658
Thanks!
Werner
>> it would be quite handy for me if I could use \featherDurations when
>> specifying manual syllable durations: [...]
>
> featherDurations= [...]
Looks like a useful addition to LilyPond – Harm, do you care to submit
a MR?
Werner
remove all Variation Fonts, in
particular the `google-noto-vf` package. It should be replaced with
non-VF Google Noto fonts. Of course, installing the 'liberation'
fonts also helps :-)
I've opened
https://gitlab.com/lilypond/lilypond/-/issues/6830
to track the update of FontConfig for LilyPond binaries.
Werner
> Lucas, you may try https://lsr.di.unimi.it/LSR/Item?id=658
> The image there is wrong, though.
>
> Werner, this happened after I changed said snippet to make it more
> obvious. What's wrong with the LSR??
I don't know, sorry. I see such a problem the very first t
>> I don't see another possibility. But I'm willing to implement 2) if
>> it fits your need.
>
> Maybe something like this? [...]
Very nice! I think this would be a good snippet for the LSR.
Werner
rposes)?
>
> I'm in touch with Wilbert.
>
> Tonight he should set up a new web hosting account just for
> frescobaldi.org so we can get access to it.
Great news! Thanks to both of you for taking care. And all the best
to Wilbert.
Werner
the Frescobaldi development team so
that a simple redirection could be added (and the old contents stored
somewhere else for archival purposes)?
> It looks like this web page is going to be updated after all, which
> is great news!
Which web page do you mean?
Werner
system* where non-trivial concepts have to be applied.
This is inevitable IMHO.
You can do an amazing job with LilyPond without touching Scheme code.
However, there will always be situations where this doesn't suffice.
Werner
> just as a gut reaction: I think this is a really great idea!
Me too.
Werner
dditionally, if you look at the examples Tina gave you can see that
the lambda function is present with and without the suggested changes,
so you are actually barking the wrong tree.
Werner
` file, and probably adding examples to the relevant
section(s) in the NR?
Werner
> `wordwrap-string-internal` is one of only three
> markup-(list)-commands flagged "internal" and thus not documented,
> but it _is_ a full blown, ready-to-use command.
Should we change this to a public function?
Werner
Hi Helge,
On Mon, May 19, 2025 at 12:57 PM Helge Kruse wrote:
%%
> That's the desired for the whole song. Except at the end. How can I get
> this closing connected bar line?
>
I do something similar with a StaffGroup - I also prefer the closing span
bar be there. Leaving the two staves hanging
ust be enclosed in a ‘\book { }’ construct.
\book {
\header { title = "A scale in LilyPond" }
\relative { c' d e f g a b c }
}
Werner
Hi Peter,
On Tue, Apr 22, 2025 at 11:42 PM Peter X wrote:
> I’m trying to figure out how to print the MIDI number of each note in a
> score using a Scheme engraver — for example, I’d like c' to print as 60, d'
> as 62, etc., during compilation.
>
%< snip >%
> What is the proper or recommended w
#x27;master' on my openSUSE
box including the English documentation with a self-compiled gs
10.05.0 (using gcc 7.5 and the `--without-tesseract` configuration
option), and everything is just fine. You should report to the Fedora
people.
Werner
> Some paper-variables are accepted in \layout. Among them is `indent`.
> Iirc, this is documented already: [...]
It is, and I've just submitted an MR to add an index entry for that
(among other minor fixes).
https://gitlab.com/lilypond/lilypond/-/merge_requests/2654
Werner
>
> This looks very nice. IMHO, the current behaviour of LilyPond is
> incorrect, and we should integrate this snippet and make it the
> default.
>
> Please open an issue in our tracker.
This is now issue #6806.
https://gitlab.com/lilypond/lilypond/-/issues/6806
Werner
> Here are the Japanese translations [...]
> Also, just to get things started with French [...]
Thanks a lot!
Werner
>> Oops, I mean
>>
>> 'Altres proves de regressió en PDF per a '
>
> Yes, no problem. Either form would work.
OK, thanks!
Werner
> Should we thus use
>
> 'D\'altres proves de regressió en PDF per a '
>
> to stay in sync?
Oops, I mean
'Altres proves de regressió en PDF per a '
Werner
;,
'PDF of MIDI regtests for ': 'Proves de regressió de MIDI en PDF per a ',
Should we thus use
'D\'altres proves de regressió en PDF per a '
to stay in sync?
Werner
or example, the implied word order is based on English and thus could
fail to fit a particular language. If you notice such problems please
report them so that we can work on it.
Werner
[*] `.po` files are maintained outside of LilyPond via the Translation
Project, see https://transla
current behaviour of LilyPond is
incorrect, and we should integrate this snippet and make it the
default.
Please open an issue in our tracker.
https://gitlab.com/lilypond/lilypond/-/issues
Werner
robably get away with many things, but I think the Gould option
> looks good.
Yep, I don't think there are other (good) choices.
Werner
27;ll find issue #14, the second most infamous bug of LilyPond...
https://gitlab.com/lilypond/lilypond/-/issues/14
Werner
istance is
something I've never seen, even in the most dense situations.
> Should it be LilyPond's default behavior?
I don't think so. For me, it is a serious deviation from standard
appearance, probably confusing the casual reader.
Werner
and Eve in the NR. Then they break
> out into multiple staves for trios, sextets, etc.
You can find such scores if you go to IMLSP and look for piano solo
arrangements of operas with 'sublinear text'.
Werner
ind a scan in the internet, sorry).
To summarize: there are indeed cases where the lyrics should jump
together with the voice from one staff to another. However, I don't
say that it makes sense to actually support that in LilyPond – it can
be worked around rather easily, and the described situations are very
rare.
Werner
hich
ideally would lead first to a snippet for the LSR and eventually to a
MR for LilyPond :-)
Werner
>> In the Internals Reference, alignAboveContext only occurs under
>> staff-ish contexts, not voice-ish ones, §2.1.x.
>
> OK, but this only gives indirect hints. I'll try to improve the
> documentation, thanks.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2620
Werner
staves, so we have a valid
technical limitation, I guess.
>> If this is a known restriction, where is it documented?
>
> In the Internals Reference, alignAboveContext only occurs under
> staff-ish contexts, not voice-ish ones, §2.1.x.
OK, but this only gives indirect hints. I'll try to improve the
documentation, thanks.
Werner
d all benefit from seeing this 'in
action' :-)
Werner
sn't work, and I get the warning
```
warning: alignAboveContext not found: V1
```
Why? If this is a known restriction, where is it documented?
Werner
Hi Kieren,
On Sun, Mar 2, 2025 at 12:06 PM Kieren MacMillan <
kie...@kierenmacmillan.info> wrote:
> Hi all,
>
> I’ve got lots of interconnected files in my libraries, and more than one
> of them may \include the same file (e.g., ChoralStaff.ily and
> VocalStaff.ily both \include Lyrics.ily).
>
>
ed in nitpicks? If I activate the red color override
in the example, the red arrow partially overlaps with the frame in the
lowest system; see attached image.
Werner
PS: I would *love* to see your code added to LilyPond. Do you think
it is mature enough? Otherwise I would add it to the LSR so that
it can be easily found by interested people.
utside-staff-priority
##f` makes the fermata actually become part of the frame.
Werner
t thus be confusing.
Consequently, I suggest to write this as
```
{ a16.*8/9[ 32*4/3] 16.*8/9 32*4/3
a16.*8/9[ 32*4/3] 16.*8/9[ 32*4/3]
...
```
instead.
Werner
ht way to
solve this because such a section could still be compressed
unfavorably in tight situations, AFAIK. Instead, I would simply give
the glissando line a minimum length (I use an exaggerated value for
demonstration purposes).
```
\relative c'' {
\time 3/4
\override Glissando.style = #'zigzag
c4 c4
c4*7/8
\tweak springs-and-rods #ly:spanner::set-spacing-rods
\tweak minimum-length #10
\glissando
\hideNotes c,,32 \unHideNotes
\bar "|"
R2.
}
```
Werner
ticulation check if it is a
> `annotate-output-event`, and then compare the grob to all
> `annotate-output-event`s that the engraver has listened to.
Would you like working on that?
Werner
> I think that I would reverse the order of the clauses so that the
> special case comes first, and reword slightly so as to make clear
> that it is a special case: [...]
Thanks; see https://gitlab.com/lilypond/lilypond/-/merge_requests/2605
Werner
> So one or other of those should replace the original example in NR
> that is decidedly long in the tooth, dating from 2.12.0.
> (Particularly as the original one doesn't really work.)
Can you prepare a patch? Or maybe even an Merge Request?
Werner
>> Use \balloonGrobText before a note or -\balloonText after a note
>> within chords.
>
> NR 1.7.2 says "typically within chords,"; it does not say "only
> within chords". Maybe the NR needs updating.
It seems that you are a native speaker. Can you suggest a better
wording?
Werner
least in the development version).
> I'm not sure what "Add" means here
It means exactly that. For example,
```
\after 4 \pp c1
```
inserts `\pp` a quarter note after 'c1' starts.
Werner
de to the NR :-)
* An updated LSR for 2.25.xx should be added to
`Documentation/snippets/new`.
* A call to `scripts/auxiliar/makelsr -N -D` adds it to
`Documentation/snippets`.
* You can than add the snippet to the appropriate `@snippets` section.
Werner
o
explicitly add a reminder to the 2.26.0 announcement note to use
`convert-ly`.
Werner
entals and I haven't
> checked how this looks on the most recent development release.
>
> What do you think about adding this to the default text
> replacements?
Rather not IMHO. This is something only experts should activate.
While it is rather innocuous in this particular case it might be
extremely frustrating for beginners to find out why LilyPond does
this. But maybe it's only me who thinks that.
Werner
If so, how could this be
improved?
Werner
is an inconvenience, yes, but I think that taking care of normal
users is more important.
Werner
ntribution to the LSR, in case you
have some time :-)
Werner
ain
> those signs [...]
Text representation forms for accidental glyphs are available in the
2.25 development series only. `\text-flat` and friends are very
recent, so you should download the latest 2.25.xx version if you want
to use these commands.
Werner
25.23"`. Attached is also an
image of the code.
Werner
tion (arg) (markup?)
#{ \markup \concat { $arg \tiny \text-sharp } #})
\score {
\new Staff { b'4 bf'4 as'4 }
\addlyrics { B\Flat B \Sharp A }
}
```
Werner
> Then I check the LSR and found that :
>
> https://lsr.di.unimi.it/LSR/Item?id=550
>
> should be corrected accordingly, as it cannot adapte to the exemple
> I gave.
Thanks, I've updated the LSR snippet.
Werner
you can check with `pdffonts` (or a similar tool) that indeed only a
single font gets used for this markup, which means that they are
identical. In other words, use 'heavy' instead of 'black'.
I've submitted a MR to add more keywords, see
https://gitlab.com/lilypond/lilypond/-/merge_requests/2587
Werner
the latter is not.
Werner
ight enjoy our 'visual index':
https://lilypond.org/doc/v2.25/Documentation/ly-examples/visualindex.pdf
Werner
> StrokeFinger was the key piece I was not finding. Sometimes in
> lilypond documentation it's a matter of finding the right keyword to
> search for.
What entries do you suggest to be added to the index?
Werner
It's an available markup command, listed at
https://lilypond.org/doc/v2.24/Documentation/notation/other
Short version:
\markup { \eyeglasses }
--
Michael
quivalent to the the JSON
metadata as distributed with SMuFL fonts like Bravura.
You can see the exact contents if you do a LilyPond build from source
code: the data can be found in `mf/out/*.lisp` and
`mf/out/*.global-lisp`.
Werner
> But I think this opens up a route via overriding the whiteout-color
> grob property and maybe also a property-defaults entry.
I suggest to file an issue, and you are more than welcome to also
provide a merge request :-)
Werner
white-out operations. Similarly, the `\whiteout` markup
command now listens to a `color` property to do the same.
Werner
em
> obsolete. Can I just add an ordinary percussion part that sounds but
> is prevented from being printed?
Always consult the LSR first :-) Have a look at
https://lsr.di.unimi.it/LSR/Item?id=1114
Werner
gt;> solution :-)
>
> I refuse that honor.
:-)
Do you have any suggestions how to improve the current situation?
Werner
has thought about that...
> (Of course, the current implementation of afterGrace makes this
> comparatively hard to achieve, since the fraction is used for
> determining the length of a skip IIRC.)
...and came to the conclusion that a global variable is the easiest
solution :-)
Werner
In full scores it is sometimes necessary to adjust the value of
`afterGraceFraction` so that it harmonizes with other notes and
rhythms. However, saying
```
afterGraceFraction =
```
only works at top-level according to the documentation. How can I
change this value mid-score?
Werner
u prepare a Merge
Request? In case you do, please remember to introduce changes in
small, incremental commits. making it easier to review the submitted
code.
Werner
y `extra-offset`.
Werner
ding LilyPond's own startup files).
Oops! The last sentence is wrong, sorry. Here is a corrected
version.
Instead, it presents LilyPond in a pristine state, before any user
input `*.ly` files has been loaded.
Werner
ting a section for
the Learning Manual (and/or for the Notation Reference) that clarifies
potential misunderstandings. Providing an update to the Glossary
might also be helpful.
> I ask again: has anyone on this list usability-tested LilyPond's
> documentation?
No.
> I'm preparing to do the work of usability-testing the docs myself.
Great!
Werner
left-handed guitars
> are unnecessary 🙂)
Well, I think this is not entirely correct. As mentioned above, a
small minority can probably benefit from left-handed instruments.
Werner
> *If* we had a page that showed all grob properties, then we could do
> that.
My bad, we actually have that :-) So yes, your suggestion is sound,
and the list of grob properties could be amended accordingly.
Werner
>>
>> ```
>> strummingHandFinger = \rightHandFinger
>> ```
>
> Yes. Also, I guess not as many left-handed players are upset about
> this as I thought.
I'm left-handed by myself (but playing the piano), and I don't feel
offended :-) By the way, AFAIK you are the very first person that ever
mentioned this issue.
Werner
to grobs have a final `-grob` or `-grobs` in their
names. Thus:
bracket-text-grob
all-element-grobs
concurrent-hairpin-grobs
...
> For pedal-text the description is misleading, though - I'd go for
> text-grob as well.
I plan to use
A pointer to the text grob of a mixed-style piano pedal.
Werner
ll in one place.
Well, patches are very welcomed :-) Right now, we don't have an
adventurous hacker who is willing to dive into such issues. Jean is
sorely missed...
Werner
l thread about musical duration, moments, etc.) In this
case, however, it will IMHO suffice to mention that LilyPond uses the
term 'right hand' for the strumming hand.
A user can also very easily define new commands that better fits the
intended purpose, for example,
```
strummingHandFinger = \rightHandFinger
```
Werner
rchive/html/lilypond-user/2021-11/msg00193.html
Werner
mething
similar)? As mentioned earlier, neither `bracket-text` nor
`pedal-text` are used anywhere in the code.
Werner
`HorizontalBracket` or `PianoPedalBracket` cannot?
Werner
hinking of is the guitar.
OK, I see. The probably simplest solution is to explicitly mention
that LilyPond uses the term 'right hand' to actually indicate the
strumming hand.
> And there's actually precedent, in that left-handed chord diagrams
> (FretBoards) are supported by Lilypond.
Well, this makes sense, because they are displayed differently.
Werner
; and 'right hand' in the
context of fretted instruments, but I don't think it makes sense to
change these long-established terms.
Werner
Well, I don't have sufficient time (and knowledge) to revise
this, sorry.
Werner
ginal MWE), it seems to work just fine. Maybe you
are using something else? In particular, I couldn't find a definition
of `\jazzOn`...
Werner
\version "2.24.0"
#(ly:set-option 'delete-intermediate-files #t)
\paper {
#(set-paper-size "letter")
indent =
es.
Manipulations the spacing is admittedly hard in LilyPond, and there
are bugs lurking around, as can be seen if you search our issue
tracker for the label 'Spacing'.
Werner
hope to reduce the space in front of notes with accidentals, so
> that accidentals can go as close as to touch the previous note. So
> what property of what grob shall I modify in this case?
Maybe the `extra-spacing-width` property of the `Accidental` grob
helps.
Werner
s might
be a bug...
Werner
dersen no.22 of 24 Etudes for Flute. You'll find it on
> IMSLP.
Thanks! And here it is :-)
Werner
27;ve never experienced a piece that starts with grace notes only
right before a bar line...
Werner
in to be able to comment. If you hover the mouse over the line
number, a small speech bubble appears, and if you click on the symbol,
you can write a comment, which becomes publicly visible after pressing
the 'Add comment now' button.
Werner
fter the "Note: There must be only one
> outer music expression ..." the following should be added: "Note
> also that if a \score is inside of a \markup or \markuplist block,
> no MIDI will be created, even with a \midi block."
Thanks. I've solved it a bit differently, please check
https://gitlab.com/lilypond/lilypond/-/merge_requests/2495
again.
Werner
> { c1 }
> \layout { }
> \midi { }
> }
> }
>
> result: no .midi file.
I don't think this is a bug: MIDI doesn't create visual markup.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2495
Werner
> Ah - it would appear that there is a typo on the doc page, which
> refers to make-center-markup (which doesn’t exist) but
> make-center-column-markup does.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2488
Werner
> Thank you for your response. Below are two examples that illustrate
> the more traditional way of displaying half note stems [...]
Thanks – so please open an issue :-)
Werner
1 - 100 of 1839 matches
Mail list logo
