#})
> >> >
> >> >
> >> > % GOOD
> >> > \floating-markup 15 -60 "some string"
> >> >
> >> > % ERROR
> >> > \floating-markup 15 -60 #{ \markup { \circle 1 } #}
> >>
> >&
% ERROR
>> > \floating-markup 15 -60 #{ \markup { \circle 1 } #}
>>
>> I made a number of points. Your "I see" only addressed a single one.
>>
>> To wit, you are still putting a Scheme expression instead of a LilyPond
>> expression in a place only a
our "I see" only addressed a single one.
>
> To wit, you are still putting a Scheme expression instead of a LilyPond
> expression in a place only admitting LilyPond syntax.
>
> The straightforward way of calling this as-is wo
ace.
>>>
>>> >
>>> > I can invoke it with:
>>> >
>>> > \floating-markup 15 -60 "some string"
>>> >
>>> > But how can I pass to the same function the following expression: {
>>> > \circle
>>>
it with:
> >
> > \floating-markup 15 -60 "some string"
> >
> > But how can I pass to the same function the following expression: {
> \circle
> > 5 } as #obj?
>
> { \circle 5 } is not a LilyPond expression. It is a fragment of markup.
> You can
t out an actual markup. Outside of markup,
\circle is not defined.
> Something like (pseudo-syntax) :
>
> \floating-markup 15 -60 #{ \circle 5 #}
#{ ... #} is a Scheme construct, not a LilyPond expression. It is used
for using LilyPond syntax inside of a Scheme expression.
If you wa
me function the following expression: { \circle
5 } as #obj?
Something like (pseudo-syntax) :
\floating-markup 15 -60 #{ \circle 5 #}
...
Thanks!
, and to the concise entry in the
list of available music functions. General syntax questions are probably
addressed better by the Learning Manual, as long as it’s pure LilyPond
syntax (without Scheme expressions).
Best, Simon
Thank you, both,
Sometimes the scope of functions? is not always clear.
Paul
On 7/1/24 12:19 PM, Valentin Petzel wrote:
Hello Paul,
\afterGrace ees2~\startTrillSpan ees1 { d16( ees) }
correct would be
ees2~\startTrillSpan \afterGrace ees1 { d16( ees) }
or
\afterGrace { ees2~\startTri
Hello Paul,
>\afterGrace ees2~\startTrillSpan ees1 { d16( ees) }
correct would be
ees2~\startTrillSpan \afterGrace ees1 { d16( ees) }
or
\afterGrace { ees2~\startTrillSpan ees1 } { d16( ees) }
(note that the latter one may have weird implications depending on
afterGraceFraction, e.g.:
\
Le lundi 01 juillet 2024 à 12:05 -0700, Paul Scott a écrit :
> Hi,
>
> This MWE works as I expect for the 1st \afterGrace but not for the 2nd
> one. In both cases I want the 16th notes in curly brackets to be the
> grace notes. I have tried several places to put the tied note.
>
> \version "2.2
Hi,
This MWE works as I expect for the 1st \afterGrace but not for the 2nd
one. In both cases I want the 16th notes in curly brackets to be the
grace notes. I have tried several places to put the tied note.
\version "2.25.17"
\fixed c''' {
r2 \afterGrace f\startTrillSpan { g16( f } ees4)\s
Thank you!
Paul
On 5/16/24 11:42, Jean Abou Samra wrote:
\set Score.repeatCommands = #'((volta ,voltaOpt))
^^^
This should be ` not ' .
> \set Score.repeatCommands = #'((volta ,voltaOpt))
^^^
This should be ` not ' .
signature.asc
Description: This is a digitally signed message part
What is wrong with the following code that gives:
programming error: Trying to interpret a non-markup object: (unquote
voltaOpt)
If it isn't clear, I'm trying to create a 3rd optional ending.
\version "2.25.16"
voltaOpt = \markup{Optional}
\fixed c' {
a1
\repeat segno 2 {
g1
\vo
Cc: lilypond-user@gnu.org
Subject: Re: \after syntax?
Hi Matt,
On Wed, Feb 21, 2024 at 10:53 AM Matthew Pierce
mailto:pierce...@hotmail.com>> wrote:
Hello all,
For hairpin positioning within a whole note, the Manual gives the syntax
\relative {
\after 2 \< c'1
}
Is ther
Hi Matt,
On Wed, Feb 21, 2024 at 10:53 AM Matthew Pierce
wrote:
> Hello all,
>
> For hairpin positioning within a whole note, the Manual gives the syntax
>
> \relative {
> \after 2 \< c'1
> }
>
> Is there an effective \after syntax for hairpin positionin
> On 21 Feb 2024, at 14:30, Matthew Pierce wrote:
>
> Hello all,
>
> For hairpin positioning within a whole note, the Manual gives the syntax
> \relative {
> \after 2 \< c'1
> }
> Is there an effective \after syntax for hairpin positioning within NON-
On Wed, Feb 21, 2024 at 7:53 AM Matthew Pierce
wrote:
> Hello all,
>
> For hairpin positioning within a whole note, the Manual gives the syntax
>
> \relative {
> \after 2 \< c'1
> }
>
> Is there an effective \after syntax for hairpin positioning within
>
Hello all,
For hairpin positioning within a whole note, the Manual gives the syntax
\relative {
\after 2 \< c'1
}
Is there an effective \after syntax for hairpin positioning within NON-whole
notes, such as the second note in this (intuitive but) nonviable expression?
\
Graham King writes:
> Many thanks David!
>
> (In the course of trying to convert the \note syntax, I discovered the
> existence of \note-by-number which solved 90% of my problem. Sorry for
> the confusing reference to \note.)
Well, \note-by-number #1 #0 #UP is essentially the s
Many thanks David!
(In the course of trying to convert the \note syntax, I discovered the
existence of \note-by-number which solved 90% of my problem. Sorry for
the confusing reference to \note.)
On Sun, 2023-09-17 at 00:38 +0200, David Kastrup wrote:
> Graham King writes:
>
> > I
Graham King writes:
> I'm trying to convert a naive Scheme function which has been broken by
> the new syntax for \note. Some arithmetic gives me the index (in this
> MNWE, 96) to a list of pairs, foo, from which I want to extract some
> markup.
>
> The 300-LOC proble
I'm trying to convert a naive Scheme function which has been broken by
the new syntax for \note. Some arithmetic gives me the index (in this
MNWE, 96) to a list of pairs, foo, from which I want to extract some
markup.
The 300-LOC problem seems to boil down to
Hi Jean,
My "struggling" was less about the tutorial, more about my failure to grasp
all the concepts.
I seem to learn the most by looking at other people's examples and trying
to understand them.
I also couldn't find the Urs Liska tutorial but I'll have a look at that
source. Thank you.
Kind regar
Le 16/10/2022 à 23:06, Colin Baguley a écrit :
I had read the Scheme tutorial but still struggled .
Admittedly, the Scheme tutorial I wrote is much too laconic on the
fundamental concept of quoting. Perhaps Urs Liska's tutorial will be
more helpful here. The link
https://scheme-book.urslisk
;Red")
> >\box \whiteout "Some text here" }
> >
> > So, my next challenge was to make this into a function so that I
> > could alter the font, size, colour,
> > position etc on the fly so to speak but I'm struggling with Scheme
> >
tion so that I
could alter the font, size, colour,
position etc on the fly so to speak but I'm struggling with Scheme
syntax here.
I've managed to work out position and fontsize, but struggling with
the rest. Here is how far I've
got. Could someone improve on this please [ and
olour,
position etc on the fly so to speak but I'm struggling with Scheme syntax
here.
I've managed to work out position and fontsize, but struggling with the
rest. Here is how far I've
got. Could someone improve on this please [ and also comment on why the
'whiteout' isn'
I thought you were canvassing user opinions.
Andrew
On 11/08/2022 3:22 pm, Jean Abou Samra wrote:
If it had been a proposal for LilyPond itself, I would have posted it
on the lilypond-devel list, not lilypond-user.
Le 11/08/2022 à 02:57, Andrew Bernard a écrit :
Ah! It read like you did propose that. Hence my screed. Phew!
If it had been a proposal for LilyPond itself, I would have posted it on
the lilypond-devel list, not lilypond-user.
Regards,
Jean
Ah! It read like you did propose that. Hence my screed. Phew!
Andrew
On 11/08/2022 2:08 am, Jean Abou Samra wrote:
Oh, I never proposed adding it to LilyPond.
mal Scheme syntax is used in all Scheme tutorials, in the Guile
manuals,
on mailing list snippets, and when printing values, so only using
Herescheme
syntax without knowing about basic Scheme syntax is likely tough.
On the
other hand, I know Scheme is off-putting to some p
On Tue, Aug 9, 2022 at 3:46 PM Jean Abou Samra wrote:
>
>
> To be honest, I have no idea if what I did here is actually a good idea
> at all (I for one won't use it). I'm just curious to see. On the one hand,
> normal Scheme syntax is used in all Scheme tutorials, i
My HP 48GX is still sitting on my desk. The best calculator ever.
I do not want an infix calculator! 30+ years old and still going strong.
Andrew
On 10/08/2022 11:20 am, Kieren MacMillan wrote
As someone who has used an HP-15C as my only calculator since 1982, I want a
POSTFIX version of Sche
n Abou Samra wrote:
Hi,
Some time ago, Jacques Menu asked on the French-speaking equivalent of
this list if it would be possible to create an infix syntax for Scheme
that would be more approachable for beginners.
Kieren MacMillan writes:
> Hi Jean,
>
> As someone who has used an HP-15C as my only calculator since 1982, I
> want a POSTFIX version of Scheme, not an INFIX version! LOL
I actually prefer Lisp dialects to FORTH. A bit of lambda calculus
makes for a more structured view.
--
David Kastrup
g equivalent of
> this list if it would be possible to create an infix syntax for Scheme
> that would be more approachable for beginners.
Jean Abou Samra writes:
> Some time ago, Jacques Menu asked on the French-speaking equivalent of
> this list if it would be possible to create an infix syntax for Scheme
> that would be more approachable for beginners.
>
> As we discussed this topic privately and he asked me ques
Am Di., 9. Aug. 2022 um 23:46 Uhr schrieb Jean Abou Samra :
>
> Hi,
>
> Some time ago, Jacques Menu asked on the French-speaking equivalent of
> this list if it would be possible to create an infix syntax for Scheme
> that would be more approachable for beginners.
>
> As
Hi,
Some time ago, Jacques Menu asked on the French-speaking equivalent of
this list if it would be possible to create an infix syntax for Scheme
that would be more approachable for beginners.
As we discussed this topic privately and he asked me questions about how
a possible implementation
Wols Lists writes:
> On 19/03/2022 20:01, David Kastrup wrote:
>> Sam Roberts writes:
>>
>>> I tried so hard to be accurate, but I missed something:
>>>
>>> On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
After experimentation, I found this worked:
\time 3/4 \partial 1 c4 |
On 19/03/2022 20:01, David Kastrup wrote:
Sam Roberts writes:
I tried so hard to be accurate, but I missed something:
On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
After experimentation, I found this worked:
\time 3/4 \partial 1 c4 |
It "works" in that pdf output looks ok, c4 is in
On Sat, Mar 19, 2022 at 1:57 PM Sam Roberts wrote:
>
> > The * syntax is described here:
> >
> > https://lilypond.org/doc/v2.22/Documentation/notation/writing-rhythms#scaling-durations
This is a good page to bookmark if you need to lookup the syntax of a command:
https://l
> The * syntax is described here:
>
> https://lilypond.org/doc/v2.22/Documentation/notation/writing-rhythms#scaling-durations
Thank you, that's perfect.
Sam
> For my more general understanding, is there documentation anywhere for
> the syntax of the argument to partial? Something that will explain the
> * syntax shown on this page?
That is simple. The argument to \partial is a duration.
>
https://music.stackexchange.com/questions/1
On Sat, Mar 19, 2022 at 2:41 PM Sam Roberts wrote:
>
> For my more general understanding, is there documentation anywhere for
> the syntax of the argument to partial? Something that will explain the
> * syntax shown on this page?
>
>
> https://music.stackexchange.com/qu
ore general understanding, is there documentation anywhere for
the syntax of the argument to partial? Something that will explain the
* syntax shown on this page?
https://music.stackexchange.com/questions/106875/how-to-write-a-pickup-measure-with-5-16-duration-in-lilypond
Thanks,
Sam
Sam Roberts writes:
> I tried so hard to be accurate, but I missed something:
>
> On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
>> After experimentation, I found this worked:
>>
>> \time 3/4 \partial 1 c4 |
>
> It "works" in that pdf output looks ok, c4 is in the pickup bar, but
> still wa
I tried so hard to be accurate, but I missed something:
On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
> After experimentation, I found this worked:
>
> \time 3/4 \partial 1 c4 |
It "works" in that pdf output looks ok, c4 is in the pickup bar, but
still warns about the bar checks, as it sho
kes 2/3 of the bar). I tried to use both approaches, no luck.
These fails the bar check, an attempt at saying 2 quarter notes:
\partial 2*1/4 c'4 |
This is syntax failure:
\partial 2/3 c'4 |
wrong type for argument 1. Expecting duration, found (cons 2 3)
I've searched for docs o
Hi,
The change to add syntax highlighting in the HTML version of the
LilyPond documentation, discussed at
https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00012.html
on the lilypond-user list and in various lilypond-devel and GitLab
threads, has now landed in the source tree and
Jean Abou Samra wrote:
[Robin]
The stroke width I see is 1px (Firefox at 100%). This makes the
stroke dominated by edge effects; the surrounding white dilutes its
colour.
Do the WCAG recommendations recognise this? If not, please don't
apply their levels to this case.
I don't know. I am
Hello Paul,
The documentation does not specify any fonts. It simply uses the and
tags. That means that the fonts used are whatever font your
browser chooses as default font, which on Windows systems appears to be
Courier for monospace and apparently in your case Georgia for the regular
text.
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 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 homegrown,
lice
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
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 homegrown, licensed
under GPL. Not sure there is anything h
[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 understa
On 04/01/2022 19:32, Jean Abou Samra wrote:
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that? Am I right that the fact that the
information stored on the user's device serves
a purpose essential to satisfying the very request
of
On 2022-01-04 11:32 am, Jean Abou Samra wrote:
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that? Am I right that the fact that the
information stored on the user's device serves
a purpose essential to satisfying the very request
Hello Jean,
The code Aaron provided is quite nice, but I suggest to rather use a linked
stylesheet like
And then use JS like
document.getElementById("syntax-highlighting") = "highlighting1.css"
This results in less complicated JS and allows for multiple styles.
Cheers,
V
[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?
On 2022-01-04 10:04 am, Valentin Petzel wrote:
The problem is that we probably want to
remember the set color scheme for longer than just the current page,
so we'd need something like cookies.
Not a problem in the slightest. But not cookies... localStorage [1].
[1]:
https://developer.mozilla
In fact it is sufficient to have multiple stylesheets and load the one you want
to switch to. The problem is that we probably want to remember the set color
scheme for longer than just the current page, so we'd need something like
cookies.
We could also do this without JS by generating multiple
On 04/01/2022 16:23, Aaron Hill wrote:
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Is that on the
On 04/01/2022 15:14, J Martin Rushton wrote:
OK, I'll admit I only skimmed it, hence "I've saved the paper to read
later"! I've got Doob's "A Gentle Introduction to TeX" and Oetiker's
"The Not So Short Introduction to LaTeX2e" both of which keep to the
fixed width convention. Again, I'll be hon
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Dynamic styles
body { font-size:
I personally find the black text much easier to read than the syntax-highlighed
one in colors. I still have young eyes, but somehow the colored text feels
tiring. Maybe this is just what I am used to, as I am still using the standard
text editor to write my .ly files. Would it be terribly
OK, I'll admit I only skimmed it, hence "I've saved the paper to read
later"! I've got Doob's "A Gentle Introduction to TeX" and Oetiker's
"The Not So Short Introduction to LaTeX2e" both of which keep to the
fixed width convention. Again, I'll be honest, I rarely use them since
I've retired thoug
J Martin Rushton writes:
> Interesting Aaron, but I do note that the paper is from 1983 and didn't
> catch on. I wonder if there is a reason for that? I've saved the
> paper to read later. Personally I don't know of a single language that
> is happy with word processor output as source code, b
Hello Robin,
as far as I know the Lilypond Documentation does not specify the font to be
used for this. So the system defaults to a standard monospace font.
So the font will depend on the system. We could ship a dedicated font with the
documentation, but I'm not sure if we want that.
Cheers,
V
Interesting Aaron, but I do note that the paper is from 1983 and didn't
catch on. I wonder if there is a reason for that? I've saved the
paper to read later. Personally I don't know of a single language that
is happy with word processor output as source code, but then I may be
proved wrong. Knu
On 2022-01-04 4:19 am, J Martin Rushton wrote:
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an
editor. Documentation flows nicely with variable pitch and fancy
hidden formats, but for code (and Lily's input is a programming
language) you just want the plain line-by-line A
ike 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.
> >
> > >
> >
> > >
'Hear hear' to these recent posts from Thomas, Paul and the two Davids!
I don't object to the fixed width, but the code font has always been
spindly compared to the rest of the documentation text. I find this
makes it harder to read anyway.
The stroke width I see is 1px (Firefox at 100%).
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 for me to see what the colour is.
I'd go e
akama 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 ability to qui
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 ability to quickly distinguis
>
> Am Sonntag, 2. Jänner 2022, 01:06:35 CET schrieb David Kastrup:
> > Jean Abou Samra writes:
> > > Hi all,
> > >
> > > There is an ongoing proposal to add syntax highlighting
> > > in LilyPond's documentation. Since it is a notable chang
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 browse a syntax-highlighted ve
#x27;t much help to you.
One way round this might be to allow the user to select colours for the
different distinguishable syntax elements (I think this has already been
suggested somewhere in this thread). And not to make it too complicated. I
personally get a bit fed up with Frescobaldi's
On 02/01/2022 16:32, Jean Abou Samra wrote:
I am colorblind (which BTW means that it's hard to distinguish certain
colors, not that everything is gray).
Sorry if I gave a wrong impression. I didn't
mean that everything actually looked gray, just
that it was the extreme imaginary case encompa
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 have
On 02/01/2022 09:34, Marc Lanoiselée via LilyPond user discussion wrote:
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.
In principle (and practice) women DO suffer this problem. It's caused by
a defect
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 have been
> chosen to have enough c
uments, see
https://lists.gnu.org/archive/html/lilypond-user/2021-11/msg00418.html
You can tweak the lexer by subclassing it in Python, read
https://pygments.org/docs/lexerdevelopment/#subclassing-lexers-derived-from-regexlexer
for how to do that. (But be prepared to discover
that recognizing LilyPond
and sorry that you will have 1001
conflicting opinions on how to progress!
Good luck.
On 2022-01-01 23:45, Jean Abou Samra wrote:
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
Le 02/01/2022 à 05:52, Jean Abou Samra a écrit :
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,
Here are the appended images. That’s the problem if you quickly send the mail
because you need to do something.
Cheers,
Valentin
signature.asc
Description: This is a digitally signed message part.
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 is not bold. Of
course it is arguable if someth
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
om
Calvin Ransom
From: lilypond-user on behalf
of Valentin Petzel
Sent: Saturday, January 1, 2022 5:53 PM
To: Jean Abou Samra; lilypond-user@gnu.org
Cc: David Kastrup; Lilypond-User Mailing List
Subject: Re: Feedback wanted: syntax highlighting in th
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 browse a syntax-highlighted ve
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-sam
Aaron Hill writes:
> convert-ly knows how to fix this:
>
>
> \override Thing #'property #'sub-property = #'value
> % ...to...
> \override Thing.property.sub-property = #'value
>
>
> It does not however seem to correct:
>
>
> variable #'key = #'value
> % ...to...
> variable.
Forgot mailinglist, sorry.
-- Forwarded message -
From: Kees van den Doel
Date: Wed, Aug 11, 2021 at 12:03 PM
Subject: Re: 5.6.1 Substitution function syntax
To: Jean Abou Samra
Thanks Jean, David,
That clarifies it, subtle stuff!
Kees
On Wed, Aug 11, 2021 at 11:45 AM Jean
Le 11/08/2021 à 20:24, David Kastrup a écrit :
Kees van den Doel writes:
Referring to
https://lilypond.org/doc/v2.22/Documentation/notation/substitution-function-syntax
I don't understand this sentence explanating "...music...":
normal LilyPond input, using $ (in pl
Kees van den Doel writes:
> Referring to
> https://lilypond.org/doc/v2.22/Documentation/notation/substitution-function-syntax
>
> I don't understand this sentence explanating "...music...":
>
>>normal LilyPond input, using $ (in places where only LilyPond co
Referring to
https://lilypond.org/doc/v2.22/Documentation/notation/substitution-function-syntax
I don't understand this sentence explanating "...music...":
>normal LilyPond input, using $ (in places where only LilyPond constructs
are allowed) or # (to use it as a Scheme value
1 - 100 of 715 matches
Mail list logo
