Le 03/12/2021 à 14:27, Павел a écrit :
Hello, I have problem with a footnote: it is not printer in the bottom
of page.
\version "2.22.1"
\score {
\header {
piece = "My piece"
opus = \markup\concat { "My opus" \footnote "*" \italic "* By
me" }
}
{ c' d' e' f' }
}
Le 01/12/2021 à 16:47, Jan Nieuwenhuizen a écrit :
Hi!
Anyone interested in taking care of this?
Greetings,
Jannke
It might be a good idea to post this on
https://lilypondforum.de/ also.
Cheers,
Jean
Le 04/12/2021 à 17:35, David Kastrup a écrit :
Simon Albrecht writes:
Hi everyone,
I have had a very weird error pop up, which doesn’t appear to be
related to a specific LilyPond version, nor was it triggered by any
recent update to OLL (though I’m using chordmode very rarely):
In the follow
Le 07/12/2021 à 22:04, Gregory Hollands a écrit :
Lukas,
I want to do this just for one score on the page, but leave all other
scores the same.
FYI I'm doing this in a lead sheet format where I have the chord
progression (and sometimes a guitar strumming pattern) in one score,
then melody and
Le 10/12/2021 à 01:13, Paolo Prete a écrit :
Hello,
please look at this snippet (tested with 2.22.0):
%
{
\time 5/4
\override TupletBracket.direction = #UP
\tuplet 3/2 { a'' a'' ais''-.}
s
\tuplet 3/2 { \once \hide Accidental a'' a'' ais''}
}
%
As you can see, the vertical gap between
Le 10/12/2021 à 18:53, Paolo Prete a écrit :
Thank you too for the tip,
Unfortunately, it seems to produce weird results in some cases, For
example: I can't set the 'padding' property in a consistent way. See
the snippet below (and please, give me a feedback, so the gitlab page
can be updated
Le 12/12/2021 à 12:53, Paolo Prete a écrit :
Hello,
I'm trying to set the font-name for a hairpin with centered text later
in the score, and not in the definition of the function.
However, my attempt, in the snippet below, doesn't work. How can I fix
this?
Thanks,
P
%
hairpinWithCentere
Le 12/12/2021 à 14:28, Paolo Prete a écrit :
Hello,
it would be good to have more control on the text centered on a hairpin.
For example: I can't shift the text vertically, and I think this is
useful because sometime the text is too near the hairpin.
I tried \lower #offset inside the mark
Le 12/12/2021 à 15:05, Paolo Prete a écrit :
On Sun, Dec 12, 2021 at 2:56 PM Jean Abou Samra
wrote:
Le 12/12/2021 à 14:28, Paolo Prete a écrit :
> Hello,
>
> it would be good to have more control on the text centered on a
hairpin.
>
> For e
Le 12/12/2021 à 21:24, Ahanu Banerjee a écrit :
Hello,
When creating a crescendo following a custom dynamic marking (e.g.,
piano subito), I am having trouble moving the start of the spanner to
a point following the dynamic markup.
What would be the best way of doing this? Example below. T
Le 12/12/2021 à 22:52, Lukas-Fabian Moser a écrit :
Hi Jean,
Use a real dynamic script. These care care of spacing for you.
\version "2.22.1"
psubito =
#(make-dynamic-script #{ \markup { p \normal-text \italic "subito" } #})
{ d'16_\psubito \cresc \repeat unfold 14 d'16 d'\f | }
Maybe I'm
Le 13/12/2021 à 04:03, Molly Preston a écrit :
Hi again.
I have a similar problem to the 8va showing up after line breaks. I
made a text spanner that's a rit.-
It shows up on the line after a break. I tried to modify the scheme
code slightly like this:
\version "2.22.1"
\new Staff
Le 13/12/2021 à 17:58, H. S. Teoh a écrit :
According to the usage manual, in order to get PNG output:
lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png
myfile.ly
But lilypond 2.23.6 aborts with this:
: In procedure scm_i_lreadparen in expression
(dynamic-wi
Le 13/12/2021 à 20:54, Jean Abou Samra a écrit :
#(display (ly:command-line-code))
Silly me. It should print nothing at all since the error is
occurring before LilyPond even starts parsing the file.
Rather, try to change scm/lily.scm by applying the attached
patch (`git apply show-command
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Paul
\version "2.23.5"
a
Le 14/12/2021 à 00:19, Paul Scott a écrit :
On 12/13/21 16:03, Jean Abou Samra wrote:
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down t
Le 14/12/2021 à 15:51, Molly Preston a écrit :
Hi Jean!
Thank you so much! That worked. I will have to keep this in mind. It's
interesting that the OttavaSpanner doesn't have something similar. Why
is that?
bound-details is a feature of so-called
"line spanners". OttavaSpanner is not
implem
Le 15/12/2021 à 19:08, Molly Preston a écrit :
Hi again!
Does anyone have issues with \allowPageTurn? I put in two page turns
in my score, but it doesn't seem to be making them. What circumstances
might create this problem?
Hard to tell without code. It may be not having
a bar line (you nee
Le 16/12/2021 à 19:03, Valentin Petzel a écrit :
Hello Jean,
I think it does make sense to apply the line spanner interface for any Spanner
that behaves pretty much like a line spanner. But then maybe it would make
sense to add some of the details of the Ottava bracket to the line spanner
inte
Le 17/12/2021 à 16:22, Molly Preston a écrit :
Someone helped with fixing the 8va so it didn't repeat 8va after the
line break. However, it is producing a solid line where the 8va is,
but only in this one place:
\version "2.22.1"
upper = {
#(define (my-callback grob)
(let* (
; ha
Le 17/12/2021 à 14:28, Molly Preston a écrit :
Thank you this helped a lot! I couldn't find it under Tempo or Markup
and didn't notice MeteonomeMark.
Here is a general method to determine what the name of a grob is:
- Go to
https://lilypond.org/doc/v2.22/Documentation/notation/lilypond-comman
Le 17/12/2021 à 21:19, Paul McKay a écrit :
Hi
Can someone show me where I'm going wrong with the following. The
piece is in 2/4. I would like the default beaming for some sections
(where there are lots of eighth notes) to group them in whole bars but
in sections where there are lots of fas
Hi Valentin,
Le 17/12/2021 à 23:23, Valentin Petzel a écrit :
Hello Molly,
The code I gave you first back then was missing a something which made it
behave badly. Harm proposed a corrected and streamlined version, and even more
compact:
#(define (my-callback grob)
(let* ((orig (ly:grob-orig
Hi,
Okay, I'll let myself sucked in this (in my opinion
unnecessarily) heated thread **for one post only**.
While I wouldn't call the proposed methods hacks, I
more or less share Paolo's dissatisfaction with the
current way footers are made customizable. What if
I wanted to write a stylesheet to
Le 20/12/2021 à 16:18, David Sumbler a écrit :
I set a piece a while ago using Lilypond 2.19.48. It consists of 2
staves, and I used \mark for some annotations that I wanted to appear
above or on barlines - mostly the "crotchet - dotted crotchet" type of
thing. Sometimes these only applied
Le 20/12/2021 à 22:28, Leo Correia de Verdier a écrit :
Dear list!
Could you help me with a clever way to copy/clone the articulations from
simultaneous notes in one sequential expression to another?
So that I could for instance enter the total articulations of a phrase as
\version "2.23.3"
<
Le 21/12/2021 à 01:20, Valentin Petzel a écrit :
Hello Jean!
That is a nice solution, but it has some issues. For one thing this will case
problem if we have a Script on a skip that is used for something like spacing
a markup (resulting in a compile error if a skip has both a script and for
exam
Le 21/12/2021 à 00:12, Leo Correia de Verdier a écrit :
Thanks a lot!
It’s a perfect solution for the typesetting, but I wonder if it would be
possible to process them earlier, so I could have them work with the articulate
script or at least consistently affect midi playback.
It may well be
Le 21/12/2021 à 21:33, David Kastrup a écrit :
Kieren MacMillan writes:
Hi again,
When I try to use it in my main file, I get this:
In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
/Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21:
Wrong type ar
Le 21/12/2021 à 21:49, David Kastrup a écrit :
Your "if" has no else path. Maybe replace it with "and", assuming that
ChordName knows how to deal with an X-offset of #f (which tends to be a
valid setting for any predicate in grob properties).
Ouch. Looking at the relevant code path uncovered
Le 21/12/2021 à 22:29, David Kastrup a écrit :
Jean Abou Samra writes:
[Valentin]
Hello Jean, hello David, hello Kieren,
you should even be able to write (if sten (ly:stencil-extent sten)),
as the stencil should always be a stencil or #f.
The two universally accepted values for any
For what it's worth, strict-note-spacing et al. are
known to have some quirks. The corresponding issues are
https://gitlab.com/lilypond/lilypond/-/issues/2630
https://gitlab.com/lilypond/lilypond/-/issues/4493
https://gitlab.com/lilypond/lilypond/-/issues/4499
Regards,
Jean
Le 26/12/2021 à 10:11, Werner LEMBERG a écrit :
[...] What must I do to
get, for example,
Balloon text
/
/
grob
this alignment? Please advise.
One solution is to wait for the patch that
ac
s the best workaround for 2.21 [which I need to use until the
edition-engraver is updated]?
Thanks,
Kieren.
commit 6df0e177b444a8f9d008cff92b8b92e39cf51727
Author: Jean Abou Samra
Date: Thu Aug 5 23:57:43 2021 +0200
Support parentheses and balloons on breakable items
This uses t
Le 29/12/2021 à 09:45, Lukas-Fabian Moser a écrit :
A cleaner and more surgical solution would be:
\version "2.18"
#(assoc-set! (assoc-ref default-script-alist "tenuto") 'padding 0.5)
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
Although this approach manipulates internal data structur
Le 26/12/2021 à 10:43, Werner LEMBERG a écrit :
[...] What must I do to get, for example,
Balloon text
/
/
grob
this alignment? Please advise.
One solution is to wait for the patch that
Le 30/12/2021 à 12:36, Lukas-Fabian Moser a écrit :
It's much worse than that: It's not the first time _I've_ been tripped
up by this (previously it was with sort!). I'll just have to write 100
copies of
"The exclamation mark in something! does not mean the function is
guaranteed to make the
Le 30/12/2021 à 22:30, David Kastrup a écrit :
An empty list does not have a last cdr.
Of course. Thanks.
Le 30/12/2021 à 23:04, Lukas-Fabian Moser a écrit :
Hi Jean,
Both of these cases seem to work the same as in
current versions if I do
[...]
SCM
assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)
{
- for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p))
+ for (SCM p = alist;
Le 31/12/2021 à 17:07, Thomas Morley a écrit :
How about:
\version "2.23.5"
#(define Bass_changes_equal_root_engraver
(lambda (ctx)
"For sequential ChordNames with same root, but different bass, the root
markup
is dropped: D D/C D/B -> D /C /B
The behaviour may be controlled by setting t
Hello Kieren, and happy new year!
Le 31/12/2021 à 04:06, Kieren MacMillan a écrit :
Hi all,
Never mind… I figured it out.
Now on to the bug (?) I actually wanted to ask about. =)
\version "2.23.4"
{
\time 1/4
\override Beam.breakable = ##t
\override Beam.positions = #'(4 . 3)
c'8
Hi all,
There is an ongoing proposal to add syntax highlighting
in LilyPond's documentation. Since it is a notable change
to the documentation reading experience, user feedback would
be appreciated. You can browse a syntax-highlighted version
of the notation manual here:
http://abou-samra.fr/hig
Le 02/01/2022 à 01:06, David Kastrup a écrit :
Jean Abou Samra writes:
Hi all,
There is an ongoing proposal to add syntax highlighting
in LilyPond's documentation. Since it is a notable change
to the documentation reading experience, user feedback would
be appreciated. You can bro
Le 02/01/2022 à 10:16, Valentin Petzel a écrit :
Hello Jean,
What I’ve done here is:
1) Make any macro that has a structural character bold. This helps in quickly
understanding the basic structure of the document. \tuplet is just a simple
music function with no real structural importance, so it
Le 02/01/2022 à 17:01, Knute Snortum a écrit :
On Sun, Jan 2, 2022 at 7:10 AM Jean Abou Samra wrote:
...
[Marc]
It will be necessary to keep an uncolored version for men (in
principle women do not have this problem) who do not see well certain
colors.
This is taken care of -- the colors
[Aaron]
It is fairly straightforward with CSS and a little JavaScript:
Yeah, that is also what I was starting to muse with
more seriously. Thanks for providing ready-made code.
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that?
[Aaron]
On 2022-01-04 11:32 am, Jean Abou Samra wrote:
Always best to consult a lawyer on legal matters.
The wife of my cousin is actually a lawyer.
Sadly (but very happily in fact), she gave
birth yesterday, so she will not be in a position
to answer before a while :-)
My layman
Le 04/01/2022 à 00:33, David Kastrup a écrit :
Flaming Hakama by Elaine writes:
In this sense, it seems like the place that has the most potential use
for helping people distinguish different data types is where the
syntax is the most complicated and dense, which is in music entry.
The abilit
Le 04/01/2022 à 23:19, Aaron Hill a écrit :
On 2022-01-04 1:42 pm, Jean Abou Samra wrote:
https://www.gnu.org/philosophy/javascript-trap.en.html
[ . . . ]
But I'm probably fretting for something that is
very easy in the end.
The code Lilypond's site would use would be entirely
Le 04/01/2022 à 11:35, Thomas Morley a écrit :
Am Di., 4. Jan. 2022 um 11:15 Uhr schrieb Paul McKay :
Hi
Speaking as someone whose eyesight isn't quite as good as it used to be,
Same problem here
I'd like to suggest that anything in a colour is also in bold so that there are
enough pixels fo
Le 05/01/2022 à 20:59, Michael Rivers a écrit :
The fingering here collides with the tempo. If the cross-staff beams
are commented out (all notes on the upper staff), the fingering
displays fine.
Is there a workaround? Am I doing something wrong?
\version "2.23.5"
global = {
\time 6/8
\t
Le 06/01/2022 à 21:36, Paulo Matos a écrit :
Hi,
I have some music I want to transcribe that has 2 parts: A and B the
music goes:
part A
part B
part A with special ending
I could of course define variables like:
\partA =
\partAtransition =
\partAending =
\partB =
and then write the music as
\p
Le 05/01/2022 à 07:51, Calvin Ransom a écrit :
Hi everyone,
I want to avoid excessive ledger lines in my score and have LilyPond
change the clef automatically.
I am creating a computer generated piece with LilyPond that covers the
entire pitch gamut.
\autochange does not work for this applicati
Le 02/01/2022 à 17:06, Paul Scott a écrit :
Happy New Year, all.
I thought I've always been able to get overlapping cues to work.
I have looked at the changes for 2.23.5
Why are the stem directions not working in this example? This
sometimes leads to:
an = \fixed c' {
a8 8
Le 06/01/2022 à 02:10, Joel C. Salomon a écrit :
A nice thing I’ve discovered in reviving my old (2.18) project is that
articulate.ly now expands repeats without `\unfoldRepeats`. A
less-nice thing is that this behavior behaves oddly around
`\alternative`:
\version "2.23.5"
\includ
Le 09/01/2022 à 03:03, Rachel Green a écrit :
Hi,
How would I allow the hairpin to cross the staff? I would like the
hairpin to be parallel with the notes as in the picture. I figured out
how to rotate it, but LilyPond does not allow the hairpin to intersect
with the staff.
I tried \override
Le 07/01/2022 à 13:12, Thomas Morley a écrit :
Am Fr., 7. Jan. 2022 um 02:31 Uhr schrieb Joel C. Salomon
:
Yesterday, I wrote:
\version "2.23.5"
\include "articulate.ly"
music = \relative c' {
c1
\repeat volta 2 {
e
\alternative {
Le 09/01/2022 à 19:06, Richard Shann a écrit :
On Sun, 2022-01-09 at 12:48 -0500, Kieren MacMillan wrote:
Hi Richard,
I guess this means it is not a well-known feature.
Not well-known, likely… but sure seems like a bug and not a feature
to me. =)
It seems to me like a superset of these tw
Le 10/01/2022 à 21:32, Rachel Green a écrit :
Thank you so much! Another problem was that I was trying commands to move
“Hairpin" rather than “Dynamic Line Spanner.” All set, thanks again!
Yes. The reason is that if there are dynamics in a row,
they should all be aligned, as in
\version "2.2
Le 12/01/2022 à 23:49, Kenneth Wolcott a écrit :
HI Carl;
There are many pieces of music in the Baroque, Classic and Romantic
periods where the same block of music is repeated without an
alternative.
This particular example is a simplified version/arrangement of a Chopin
Waltz.
The p
Le 14/01/2022 à 10:39, Lukas-Fabian Moser a écrit :
Hi Rajesh,
Am 14.01.22 um 01:44 schrieb Rajesh Baskar:
I'm tying to display a question mark at the center of the 1st measure
in a 2 measure score.
I have got this working with hard-coding the offset (3 . 4.5) but
this will not work when
Le 14/01/2022 à 20:41, Valentin Petzel a écrit :
Hello Richard,
The file you’ve given us has a lot of nonsensical quoting in lines 149-153.
Actually, not completely nonsensical, but legacy. There used to
be one more level of quoting inside stencil expressions until
commit 06ba7f0823a14da7733
Le 18/01/2022 à 18:01, Simon Albrecht a écrit :
Hi everyone,
I wanted to set up some customisable headings using #(string-upcase
"string"), but it doesn’t work on German umlauts, so I came upon
string-locale-upcase on this page:
https://www.gnu.org/software/guile/docs/docs-2.2/guile-ref/Char
Le 18/01/2022 à 19:14, Rajesh Baskar a écrit :
Thanks Lukas and Jean for your help.
There is an issue with the below solution. Whenadding << and >> the
visual is correct but while playing the score the first measure notes
all play together. I'm guessing it's because of << >>. Is there a way
Le 18/01/2022 à 20:37, Simon Albrecht a écrit :
On 18/01/2022 18:52, Jean Abou Samra wrote:
Because this is documentation for Guile 2
and current releases of LilyPond still have
Guile 1.8.
Thanks for the speedy reply! I wasn’t sure whether the switch to Guile
2 had already been made. I got
Le 19/01/2022 à 00:40, Rajesh Baskar a écrit :
Hi Jean,
Here is the complete code.
Yes. Here is a simplified example:
\version "2.22.1"
\score {
{
\startMeasureCount
<<
\hideNotes b'4 a' g' a'
\new Voice { R1 }
>>
\stopMeasureCount
}
\midi { }
\layout {
... this applies to me as well, so I haven't tested
anything else and don't intend to delve deeper than
this for now.
Best,
Jean
From 84078085af9d83e4f5fa3bfa93f7804e99803698 Mon Sep 17 00:00:00 2001
From: Jean Abou Samra
Date: Wed, 19 Jan 2022 01:37:41 +0100
Subject: [PATCH] Qui
Le 19/01/2022 à 01:45, Jean Abou Samra a écrit :
Le 18/01/2022 à 20:43, Simon Albrecht a écrit :
Dear list,
I have started using the experimental 2.23.5 build with Guile 2.2 [1]
and it turns out to be incompatible with the core of openLilyLib.
Here are the error messages I got—it may be
Le 19/01/2022 à 09:46, Thomas Scharkowski a écrit :
Hallo,
I’d like to replace the arpeggioBracket by a curly bracket / brace.
Thank your for your help!
Here's a stencil callback reading the vertical start
and end positions of the arpeggio and printing a bracket
accordingly:
\version "2.22.1
Le 19/01/2022 à 13:58, Thomas Scharkowski a écrit :
Am 19.01.2022 um 13:09 schrieb Jean Abou Samra :
Le 19/01/2022 à 09:46, Thomas Scharkowski a écrit :
Hallo,
I’d like to replace the arpeggioBracket by a curly bracket / brace.
Thank your for your help!
Here's a stencil cal
Le 19/01/2022 à 14:47, Thomas Scharkowski a écrit :
This does not work for me (I did change of course PianoStaff to Staff).
To get the „normal“ brackets I use:
\override Staff.Arpeggio.stencil = #ly:arpeggio::brew-chord-bracket
This works for me:
\version "2.22.1"
spanArpeggioBrace =
\once \
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
Good morning,
trying to understand the programming a bit better, I managed to
transform the mixed command definitions to scheme code (see below).
I've learnt the following in the process; should some of it be made
more explicit in the manual?
plans of similar scope, and [I] work on LilyPond as a
hobby in otherwise already LilyPond development
is for me a hobby in already otherwise busy weeks.
Talk about busy weeks...
Le 22/01/2022 à 14:27, Valentin Petzel a écrit :
Hello Kieren,
I think you meant someone else :-)
that seems to be correct.
One could also try something like this.
It deserves to be mentioned that \repeat segno has
been implemented by Dan Eble in the development
branch. It will be inclu
y now ...
Le 22/01/2022 à 10:47, Bernhard Fisseni a écrit :
Good morning, Jean,
thank you very much for your detailed explanation! This helps me to
understands things a bit better.
Jean Abou Samra schrieb am 21.01.22 um 19:30:
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
- Ther
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a "diff
file" describing the musical differences *as would be perceived by a human reading
the score*. For example, given
Score #1 = \score { \new Staff << { c'1
Le 23/01/2022 à 00:14, Jean Abou Samra a écrit :
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a
"diff file" describing the musical differences *as would be perceived
by a human reading the scor
not accept ChoirStaff, so
the GrandStaff actually does not receive any music at all
and ChoirStaff contexts are inserted inside Score. This
has the consequence that the expected brace is not
inserted. There are a number of similar cases. They
were sorted out in the development series by this
change in t
Le 27/01/2022 à 19:41, Kieren MacMillan a écrit :
Hi all,
I'm trying to engrave rap phrases on a strict grid (cf.
https://www.passionweiss.com/2013/04/09/let-the-rhythm-hit-em-a-look-at-the-musical-notation-of-rap).
Is this possible in Lilypond? (I can't believe I'm actually asking that
quest
Le 28/01/2022 à 08:27, Jefferson Skinny a écrit :
Hi,
I noticed that grace notes do not follow the same as normal notes.
Normally, notes which are placed beyond ledger lines will have longer
stems to avoid clashing with them. Certainly, it is possible to tweak
the stems individually, but is i
Le 28/01/2022 à 13:45, Simon Albrecht a écrit :
Dear list,
I have encountered some unexpected behaviour with tags and tagGroups.
In the following example, I thought the two staffs should look the
same, even without the \removeWithTag command, but they don’t:
\version
Le 30/01/2022 à 22:20, Simon Albrecht a écrit :
Hi List,
is there an equivalent to self-alignment-X for the left bound text of
a DynamicTextSpanner? See below.
Best, Simon
\version "2.23.5"
{
1-\tweak self-alignment-X 1 \fff
1
% this causes alignment to just fail indiscriminately
%
Le 31/01/2022 à 12:39, Paulo Matos a écrit :
Hi,
I am arranging some music and finding some issues with regards to
styling of objects.
For example: http://lilybin.com/ydeys1/1
How can I style the accidentals and the numbers in the TabStaff?
Add overrides for the relevant grobs:
\override
Le 31/01/2022 à 13:13, Jean Abou Samra a écrit :
That one is much more complicated. You can find a workaround at
https://lists.gnu.org/archive/html/lilypond-user-fr/2021-06/msg00081.html
Is it me who wrote that??
\version "2.22.1"
\header {
title = "Test"
}
Le 31/01/2022 à 17:33, David Niles a écrit :
Good Morning,
Please remove my email address from ALL OF YOUR MAILINGS. I am not
interested and do not want to receive them.
Thank you,
David Niles
ekj...@gmail.com
That is not up to the administrator but up to yourself.
Please go to
https://li
Le 01/02/2022 à 18:34, Valentin Petzel a écrit :
Thank you. As it seems prior to 2.23 the Volta Bracket engraver would override
the text property even if you had manually specified this. So we can either
directly modify this in the repeat command (which I consider a bit ugly), or
try some work
Hi,
Lately I've found myself a couple times duplicating answers
already provided on this list by others up to almost three
hours earlier because I had not received these replies yet.
Now the little delay for posts to get in inboxes is a quirk
inherent to mailing lists, but three hours seems a bit
Le 01/02/2022 à 20:10, Valentin Petzel a écrit :
Hello David,
An assignment basically adds a pair (symbol, value) to some assignment table.
So shouldn’t it be possible to parse a file with a new assignment table and
then convert this assignment table into a scheme accessible structure?
I do not
Le 01/02/2022 à 23:14, Jean Abou Samra a écrit :
Well, if you are ready to get evil, you can do
\version "2.23.5"
includeNamespace =
#(define-scheme-function (filename) (string?)
(let ((new-parser (ly:parser-clone)))
(ly:parser-parse-string
new-parser
(format #f
> Le 5 févr. 2022 à 11:42, Kevin Barry a écrit :
>
> Hi Kenneth,
>
> I think you can fix the problem with the relative positioning by
> setting the 'outside-staff-priority, e.g.:
>
> \tweak #'outside-staff-priority #0 \ottava 1
I think (cannot verify this weekend) that this is only going t
> Le 5 févr. 2022 à 17:34, Kenneth Wolcott a écrit :
>
> Hi Kevin;
>
> I commented that line out because I get an error when engraving it.
>
> GNU LilyPond 2.22.1 (running Guile 2.2)
> Processing `Jeanie_With_The_Light_Brown_Hair.ly'
> Parsing...
> Jeanie_With_The_Light_Brown_Hair.ly:56:4:
> Le 5 févr. 2022 à 20:10, Rip _Mus a écrit :
>
> Good evening everyone,
> do you know if there is a complete reference (perhaps with tutorials) of the
> use of the Scheme functions?
> In the Lilypond reference, from time to time, some functions are explained,
> but it seems to me that a prec
> Le 6 févr. 2022 à 10:16, Aaron Hill a écrit :
>
> I have for quite some time just relied on the default behavior where bar
> numbers are printed only for the first measure in each line (save the very
> first measure). This works reasonably well as my musicians are able to
> locate measure
> Le 6 févr. 2022 à 11:54, Valentin Petzel a écrit :
>
> Thus I think this would be a sensible default. Is there any good reason
> against using this by default?
I wondered about that as well when I split the barNumberVisibility test and
submitted the pending MR to no longer require \bar
> Le 6 févr. 2022 à 18:39, Trinton a écrit :
>
> Hi folks,
>
> Since adding dashed slurs to my score using the \slurDashed command, I've
> been unable to concatenate the segments of my score, getting this error:
> [48]ERROR: Wrong type (expecting exact integer): # Trill_spanner_engraver >
> I
> Le 6 févr. 2022 à 22:52, Lukas-Fabian Moser
> I'm just still confused as to the terminology of event "classes" vs. event
> "types" etc. But that's something for next week...
Allow me to take advance on next week by an hour, then (in Paris time, that
is). The terms "music class" and "event
Le 05/02/2022 à 12:50, Richard Shann a écrit :
On Sat, 2022-02-05 at 11:30 +, Richard Shann wrote:
Is there a way to drop the line that is drawn below the systems above
the footnotes?
Sorry for asking before searching the mailing-list archives,
\paper { footnote-separator-markup = ##f }
i
Le 31/01/2022 à 16:41, Leo Correia de Verdier a écrit :
31 jan. 2022 kl. 15:56 skrev Paulo Matos :
Ah - grobs is the technical term I needed.
Where's the best place to find the available grobs that I can style?
https://lilypond.org/doc/v2.21/Documentation/internals/all-layout-objects
Here
Le 07/02/2022 à 23:23, Murphy Sifa a écrit :
Hi Lilypond Software,
We are analysing our suite of SaaS vendors for exposure to the log4j
vulnerability. I can’t find a statement on your page about the
products that La Trobe is using.
Can you please provide me with the log4j vulnerability stat
Le 07/02/2022 à 20:17, Lukas-Fabian Moser a écrit :
Wow. Thanks. (And luckily Paris and Salzburg share a time zone.)
So here's what made me stumble: In scm/scheme-engravers.scm, we find
(define-public (event-has-articulation? event-type stream-event)
"Is @var{event-type} in the @code{articula
401 - 500 of 2251 matches
Mail list logo