Re: Feedback wanted: syntax highlighting in the LilyPond documentation
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 browse a syntax-highlighted version of the notation manual here: http://abou-samra.fr/highlighting-demo/notation/index.html For comparison, this is the current notation manual: https://lilypond.org/doc/v2.23/Documentation/notation/index.html The main questions are: what do you think of the principle? And is the color scheme good enough? I just followed the discussion without much attention because I did not think that it would affect me whether or not there was syntax highlighting. That probably was a mistake. Taking a random example: There is a wild mixture of colors and font styles without apparent rhyme or reason. I don't see that it helps legibility or conveys any useful categories. I cannot even figure out what it thinks it is doing. \layout, \context, \remove are reserved words in the syntax and are printed in boldface and black. So is \override which is printed in normalface blue, like \relative and \repeat. But \relative is a music function while \repeat is a reserved word. Beam.breakable is printed in red while unfold is printed in blue. While you and me have the perspective of parser keywords vs. music functions, I think we can agree that this is mostly irrelevant to highlighting. A typical user does not need or want to care whether \repeat is implemented as a token or a music function, and probably does not know the difference anyway (until they try to redefine it, in which case the lexer gives them a friendly warning). What is relevant is clearly the function in input. From this perspective, the highlighting applies one rule of thumb: what yields an articulation is purple, everything else that yields music is blue. From this point of view, the example you show is consistent. The case of \override in a context definition is somewhat special since it bypasses music, but it would be awkward to have it in a different color than \override in the flow of music, particularly since something like \once \override in a context definition works via music (and we briefly discussed making \override work the same some months ago). However, because all rules are there to be broken, there are notable exceptions to the "what yields music is blue" rule, such as \new. There are two reasons to this. One is that \new pairs with \context in music, but \context should really be a keyword in output definitions, and the lexer does not (yet) try to distinguish between these cases. The other reason is that \new drives the structure of many examples and highlighting it in bold seemed to help grasping good enough a number of them to be worth an exception. So this is basically an admittedly handwaving reasoning of "you want to see this first because it is an important structuring element". Other important such exceptions are mode switchers such as \addlyrics and friends. Now, Valentin proposes a scheme where (most?) music functions are bold too, so this could be reconsidered. unfold is blue because it's considered part of the essence of the "\repeat something" command. It don't pretend that is the best choice, and since I eventually decided not to highlight clef names in blue I should likely revert it. Beam.breakable is red like all grob property paths. There is apparently a large collection of colors To be exact, five colors in total if you count grey. That's not exactly what I would call a large collection ... and some font styles Just bold for keywords. Nothing more. [snipped] [Valentin] Hello Jean, hello David, I do like the idea, but I do agree with David to some extent. Syntax highlighting should emphasize the structure of the file and thus make reading easier. But if it gets too colorful in terms of contrast of colors the colors simply distract you. For example there is no good reason for coloring all numbers some outstanding way. Frescobaldi does this, but that just creates distracting dots of color in the code. And numbers tend to be quite discernible, so you do not really need a special color to mark them. It seemed to help discerning articulations such as [( from dotted durations and also those with multipliers. Not that it matters so much to me though. Or perhaps I should use a less bright color? That being said your color scheme is much better than Frescobaldi’s scheme, which is appallingly distracting. See the appended file for a comparison of Frescobaldi and KDE Kate (which is by no means perfect, but at least an improvement...). I think your color scheme could be improved easily by doing something like in the other screenshot (taking the same snippet as David). Ok, thanks for trying out, but could you explain what it does more precisely? Specifically, what is setting apart \tuple
Re: Feedback wanted: syntax highlighting in the LilyPond documentation
Hi Jean, I think it sounds like a really good idea. Would it be possible to have a menu for changing the highlighting settings to create some customizability? I'm not familiar with web development at all so I don't know if this would be difficult to implement. Good luck! Calvin Ransom 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 the LilyPond documentation Hello Jean, hello David, I do like the idea, but I do agree with David to some extent. Syntax highlighting should emphasize the structure of the file and thus make reading easier. But if it gets too colorful in terms of contrast of colors the colors simply distract you. For example there is no good reason for coloring all numbers some outstanding way. Frescobaldi does this, but that just creates distracting dots of color in the code. And numbers tend to be quite discernible, so you do not really need a special color to mark them. That being said your color scheme is much better than Frescobaldi’s scheme, which is appallingly distracting. See the appended file for a comparison of Frescobaldi and KDE Kate (which is by no means perfect, but at least an improvement...). I think your color scheme could be improved easily by doing something like in the other screenshot (taking the same snippet as David). Cheers, Valentin 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 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/highlighting-demo/notation/index.html > > > > For comparison, this is the current notation manual: > > > > https://lilypond.org/doc/v2.23/Documentation/notation/index.html > > > > The main questions are: what do you think of the principle? > > And is the color scheme good enough? > > I just followed the discussion without much attention because I did not > think that it would affect me whether or not there was syntax > highlighting. That probably was a mistake. Taking a random example:
Re: Make Grid take an edit id
Sorry, that was not meant that way. This was intended to demonstrate the
usefulness of having such an id for the line, no matter if it is a separate
property or a value of details.
(Having one id property for all grobs does seem reasonable.)
About the other thing: It gets more complicated for both the implementation
and the user. For example in a situation where the number of encompassed
Staves is not fixed, e.g. when Staves are added or removed during the music (as
shown in the appendend very bad example) the context name based approach is
rather complicated, as for each change to the staves we’d need to create a new
grid. Instead with an id based approach it is sufficient to do something like
\startGrid id moment
for each staff in the place it is needed and
\stopGrid id
once we want to take the staff out of the grid.
Cheers,
Valentin
<<
\new Staff {
\set Staff.gridInterval = #(ly:make-moment 1/2)
\repeat unfold 10 { c''16 d'' e'' b' }
\unset Staff.gridInterval
c''2~ c''1
}
\new Staff {
b'2
\set Staff.gridInterval = #(ly:make-moment 1/2)
\repeat unfold 10 {
\tuplet 3/2 { b'16 d'' c'' d'' f'' e'' }
}
\unset Staff.gridInterval
b'1
}
\new Staff {
a'1
\set Staff.gridInterval = #(ly:make-moment 1/2)
\repeat unfold 5 {
\tuplet 5/4 { a'8 c'' f'' g'' d'' }
}
\unset Staff.gridInterval
a'2
}
\new Staff {
g'1~ g'2
\set Staff.gridInterval = #(ly:make-moment 1/2)
\repeat unfold 5 {
\tuplet 7/8 { g'16 f' d' d'' c'' b' a' }
}
}
>>
\layout {
\context {
\Staff
\consists "Grid_point_engraver"
}
\context {
\Score
\consists "Grid_line_span_engraver"
}
}
signature.asc
Description: This is a digitally signed message part.
Re: Feedback wanted: syntax highlighting in the LilyPond documentation
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 version > of the notation manual here: > > http://abou-samra.fr/highlighting-demo/notation/index.html > > For comparison, this is the current notation manual: > > https://lilypond.org/doc/v2.23/Documentation/notation/index.html > > The main questions are: what do you think of the principle? > And is the color scheme good enough? I just followed the discussion without much attention because I did not think that it would affect me whether or not there was syntax highlighting. That probably was a mistake. Taking a random example: There is a wild mixture of colors and font styles without apparent rhyme or reason. I don't see that it helps legibility or conveys any useful categories. I cannot even figure out what it thinks it is doing. \layout, \context, \remove are reserved words in the syntax and are printed in boldface and black. So is \override which is printed in normalface blue, like \relative and \repeat. But \relative is a music function while \repeat is a reserved word. Beam.breakable is printed in red while unfold is printed in blue. There is apparently a large collection of colors and some font styles but the application appears rather haphazard, being neither systematically related to the actual category of the tokens nor to their function in user input. There does not appear to be a coherent payback for the inherent lowering of readability (and printability) from the lower contrast of colored passages. What is the information you want to convey better? -- David Kastrup
Feedback wanted: syntax highlighting in the LilyPond documentation
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/highlighting-demo/notation/index.html For comparison, this is the current notation manual: https://lilypond.org/doc/v2.23/Documentation/notation/index.html The main questions are: what do you think of the principle? And is the color scheme good enough? Thanks in advance, Jean
Re: point-and-click default
May I just fan the fire by saying that on kde this works out of the box? That being said, the only really usable pnc implementation is Frescobaldi, as that one will keep track while you’re editing the file and thus always point to the right thing. And I don’t see much of a problem with disabling pnc by default, but it would not change much as most people would probably activate it somewhere and still forget to deactivate it for sharing. Cheers, Valentin Am Donnerstag, 30. Dezember 2021, 18:22:42 CET schrieb David Zelinsky: > David Zelinsky writes: > > Tom Sgouros writes: > >> For those of us just catching up, can someone explain how to see the > >> metadata? I guess this is more of a PDF question, but while I have some > >> experts' attention... > >> > >> Thank you, > >> > >> -Tom > > > > I can only tell you about evince, the pdf reader I use. But I expect it > > should be the same in most pdf readers. > > > > If you hover the mouse pointer over a notehead, it displays the URI that > > > > will be looked up when you click there. It will look like this: > > textedit > > > > where is the absolute path to the lilypond source > > file, and and are the starting and ending > > positions of the text defining the note in question. > > > > -David > > Sorry, I meant to say also that is the line number in the source > file where the note definition appears. > > In evince on my Ubuntu system, clicking on the note elicits an error, > because evince does not know what to do with a "textedit:..." link. > Section 4.1 of the Usage Manual (under 4. External Programs) explains > how to make it work. > > -David signature.asc Description: This is a digitally signed message part.
Re: Multiple grid lines in the same score
Hello Lib,
https://gitlab.com/lilypond/lilypond/-/merge_requests/1099
I’ve got a first version up, which easily can do stuff as in the appended file.
The shift on the first one requires a manual override so far.
Cheers,
Valentin
Am Samstag, 1. Jänner 2022, 21:17:52 CET schrieb Lib Lists:
> Hi Valentin,
> wow, thanks, if you have the time that would be great!
>
> To clarify what I mean, here attached is an example made with
> Inkscape. I suspect that a dashed line would work better than a
> coloured one, but anything that would differentiate the two grid lines
> would work.
>
> Cheers,
> Lib
>
> On Sat, 1 Jan 2022 at 18:15, Valentin Petzel wrote:
> > Hello Lib, I think I can implement something for that, give me a day or
> > two.
> >
> > Cheers,
> > Valentin
> >
> > Am Samstag, 1. Jänner 2022, 15:56:18 CET schrieb Lib Lists:
> > > Hello everybody, and happy new year!
> > >
> > > In the example below I would like to add another set of grid lines to
> > > show the triplet subdivisions in the lower staff. Moreover, I'd like
> > > to colour the two grid lines differently. I couldn't find any example
> > > and I'm not sure whether this is actually possible.
> > >
> > > Alternatively, what would be the best strategy to add lines to connect
> > > notes in different staves?
> > >
> > > Thank you in advance for any help!
> > >
> > > Lib
> > >
> > > - - -
> > >
> > > \version "2.22.1"
> > > \score {
> > >
> > > <<
> > >
> > > \new Staff {
> > >
> > > \time 2/8
> > > \relative c'' {
> > >
> > > \override TupletBracket.bracket-visibility = ##t
> > > \tuplet 3/2 {\tuplet 5/4 {a32[ a a a a]} \tuplet 5/4 {a32[ a a
> > >
> > > a a]}\tuplet 5/4 {a32[ a a a a]}}
> > >
> > > }
> > >
> > > }
> > > \new Staff {
> > >
> > > \relative c {
> > >
> > > \clef bass
> > > \override TupletBracket.bracket-visibility = ##t
> > > \tuplet 5/4 {\tuplet 3/2 {e32[ e e]} \tuplet 3/2 {e32[ e
> > >
> > > e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e
> > > e]}}
> > >
> > > }
> > >
> > > }
> > >
> > > \layout {
> > >
> > > \context {
> > >
> > > \Staff
> > > \consists "Grid_point_engraver"
> > > gridInterval = #(ly:make-moment 1/12)
> > >
> > > }
> > > \context {
> > >
> > > \Score
> > > \consists "Grid_line_span_engraver"
> > >
> > > }
> > >
> > > }
> > >
> > > }
grid-lines-ids.pdf
Description: Adobe PDF document
\version "2.23.6"
\score {
<<
\new RhythmicStaff
{
\once\override Score.GridLine.X-offset =
#(lambda (grob)
(let ((id (ly:grob-property grob 'grid-id)))
(if (eq? id 'A) -0.1 0)))
\tuplet 3/2 {
\tupletSpan 8*2/3
\tuplet 5/4 \repeat unfold 3 { c32[ c c c c] }
}
}
\new RhythmicStaff
{
\tuplet 5/4 {
\tupletSpan 16*4/5
\tuplet 3/2 \repeat unfold 5 { c32[ c c] }
}
}
>>
\layout {
\context {
\RhythmicStaff
\consists "Grid_point_engraver"
\override TupletBracket.bracket-visibility = ##t
idGridIntervals = #`((A . ,(ly:make-moment 1/12))
(B . ,(ly:make-moment 1/20)))
}
\context {
\Score
\consists "Grid_line_span_engraver"
\override GridLine.color =
#(lambda (grob)
(let ((id (ly:grob-property grob 'grid-id)))
(if (eq? id 'A) red
(if (eq? id 'B) blue black
}
}
}
signature.asc
Description: This is a digitally signed message part.
Re: Multiple grid lines in the same score
Hi Valentin,
wow, thanks, if you have the time that would be great!
To clarify what I mean, here attached is an example made with
Inkscape. I suspect that a dashed line would work better than a
coloured one, but anything that would differentiate the two grid lines
would work.
Cheers,
Lib
On Sat, 1 Jan 2022 at 18:15, Valentin Petzel wrote:
>
> Hello Lib, I think I can implement something for that, give me a day or two.
>
> Cheers,
> Valentin
>
> Am Samstag, 1. Jänner 2022, 15:56:18 CET schrieb Lib Lists:
> > Hello everybody, and happy new year!
> >
> > In the example below I would like to add another set of grid lines to
> > show the triplet subdivisions in the lower staff. Moreover, I'd like
> > to colour the two grid lines differently. I couldn't find any example
> > and I'm not sure whether this is actually possible.
> >
> > Alternatively, what would be the best strategy to add lines to connect
> > notes in different staves?
> >
> > Thank you in advance for any help!
> >
> > Lib
> >
> > - - -
> >
> > \version "2.22.1"
> > \score {
> > <<
> > \new Staff {
> > \time 2/8
> > \relative c'' {
> > \override TupletBracket.bracket-visibility = ##t
> > \tuplet 3/2 {\tuplet 5/4 {a32[ a a a a]} \tuplet 5/4 {a32[ a a
> > a a]}\tuplet 5/4 {a32[ a a a a]}}
> > }
> > }
> > \new Staff {
> > \relative c {
> > \clef bass
> > \override TupletBracket.bracket-visibility = ##t
> > \tuplet 5/4 {\tuplet 3/2 {e32[ e e]} \tuplet 3/2 {e32[ e
> > e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e
> > e]}}
> > }
> > }
> >
> > \layout {
> > \context {
> > \Staff
> > \consists "Grid_point_engraver"
> > gridInterval = #(ly:make-moment 1/12)
> > }
> > \context {
> > \Score
> > \consists "Grid_line_span_engraver"
> > }
> > }
> > }
Re: point-and-click default
On 30/12/2021 17:22, David Zelinsky wrote: In evince on my Ubuntu system, clicking on the note elicits an error, because evince does not know what to do with a "textedit:..." link. Section 4.1 of the Usage Manual (under 4. External Programs) explains how to make it work. Nor does my Windows setup ... When it works, it's useful, but it's certainly not a novice hack if it doesn't work out-of-the-box. (Yes I know it's bog-standard nix, but my original background was minicomputers, and it still feels alien to me.) Cheers, Wol
Re: Multiple grid lines in the same score
Hello Lib, I think I can implement something for that, give me a day or two.
Cheers,
Valentin
Am Samstag, 1. Jänner 2022, 15:56:18 CET schrieb Lib Lists:
> Hello everybody, and happy new year!
>
> In the example below I would like to add another set of grid lines to
> show the triplet subdivisions in the lower staff. Moreover, I'd like
> to colour the two grid lines differently. I couldn't find any example
> and I'm not sure whether this is actually possible.
>
> Alternatively, what would be the best strategy to add lines to connect
> notes in different staves?
>
> Thank you in advance for any help!
>
> Lib
>
> - - -
>
> \version "2.22.1"
> \score {
> <<
> \new Staff {
> \time 2/8
> \relative c'' {
> \override TupletBracket.bracket-visibility = ##t
> \tuplet 3/2 {\tuplet 5/4 {a32[ a a a a]} \tuplet 5/4 {a32[ a a
> a a]}\tuplet 5/4 {a32[ a a a a]}}
> }
> }
> \new Staff {
> \relative c {
> \clef bass
> \override TupletBracket.bracket-visibility = ##t
> \tuplet 5/4 {\tuplet 3/2 {e32[ e e]} \tuplet 3/2 {e32[ e
> e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e
> e]}}
> }
> }
>
> \layout {
> \context {
> \Staff
> \consists "Grid_point_engraver"
> gridInterval = #(ly:make-moment 1/12)
> }
> \context {
> \Score
> \consists "Grid_line_span_engraver"
> }
> }
> }
signature.asc
Description: This is a digitally signed message part.
Re: Beam not breaking
Hi Jean, > happy new year! Happy 2022 to you and yours! > I've added this example to > https://gitlab.com/lilypond/lilypond/-/issues/3415 > I've also posted a workaround Thanks for doing both of those — your workaround certain beats the five-tweak edition-engraver injection it replaces. :) All the best, Kieren.
Multiple grid lines in the same score
Hello everybody, and happy new year!
In the example below I would like to add another set of grid lines to
show the triplet subdivisions in the lower staff. Moreover, I'd like
to colour the two grid lines differently. I couldn't find any example
and I'm not sure whether this is actually possible.
Alternatively, what would be the best strategy to add lines to connect
notes in different staves?
Thank you in advance for any help!
Lib
- - -
\version "2.22.1"
\score {
<<
\new Staff {
\time 2/8
\relative c'' {
\override TupletBracket.bracket-visibility = ##t
\tuplet 3/2 {\tuplet 5/4 {a32[ a a a a]} \tuplet 5/4 {a32[ a a
a a]}\tuplet 5/4 {a32[ a a a a]}}
}
}
\new Staff {
\relative c {
\clef bass
\override TupletBracket.bracket-visibility = ##t
\tuplet 5/4 {\tuplet 3/2 {e32[ e e]} \tuplet 3/2 {e32[ e
e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e e]}\tuplet 3/2 {e32[ e
e]}}
}
}
>>
\layout {
\context {
\Staff
\consists "Grid_point_engraver"
gridInterval = #(ly:make-moment 1/12)
}
\context {
\Score
\consists "Grid_line_span_engraver"
}
}
}
Re: How to implement a "5-3" fingering (Piano) (LP 2.22)
Well, would not call it reduntant and unnecessary and certainly not stupid. It
served purpose to detect that the German version of the documentation needs an
update at this point, and with the further clarification serves the
German-speaking part of the community which would likely get redirected to the
German version of the documentation just like you.
For those getting redirected to the non-German language versions of the docs
it's indeed redundant and a bit confusing.
> On 1 Jan 2022, at 11:26, Valentin Petzel wrote:
>
> Hello Hans,
>
> My bad, this must have been changed recently. Knute Snortum asked the same
> thing in October, at which point the docs still had the old way. And when I
> checked the stupid automatic language selector (why the heck do we have
> this?)
> of course delegated me to the german documentation which is of course the
> only
> one still using the old snippets.
>
> So my remark becomes stupid, redunant and unnescessary.
> Cheers,
> Valentin
>
> Am Samstag, 1. Jänner 2022, 11:05:41 CET schrieb Hans Aikema:
>> Valentin,
>>
>> your remark confuses me.
>> In what way is your suggested syntaxt different from what's in the docs?
>>
>> \relative {
>> c''4-1 d-2 f\finger \markup \tied-lyric "4~3" c\finger "2 - 3"
>> }
>>
>> I only see a few spaces which afaik only icrease readability, but apparently
>> I overlook something.
>>
>> regards,
>> Hans
>>
On 1 Jan 2022, at 10:56, Valentin Petzel wrote:
>>>
>>> Hello Ken, hello David,
>>>
>>> the way given in the documentation is not particularly good, as this won't
>>> produce a Fingering grob but a TextScript grob, which cannot be
>>> positioned the same way.
>>>
>>> Much better would be to use
>>>
>>> e-\finger "5-3"
>>> or
>>> e-\finger\markup\tied-lyric "5~3"
>>> or something.
>>>
>>> Cheers,
>>> Valentin
>>>
>>> 01.01.2022 03:25:13 Kenneth Wolcott :
HI David;
Thank you. Read right past it, missing it entirely.
Ken
> On Fri, Dec 31, 2021 at 6:03 PM David M. Boothe, CAS
> wrote:
>
> http://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff
>
> The second example under the heading "Fingering Instructions" gives you
> a couple of options.
>
> dB
>
> On Fri, Dec 31, 2021, 8:51 PM Kenneth Wolcott
> wrote:
>> HI;
>>
>> How to implement a "5-3" fingering (Piano) (LP 2.22)
>>
>> See attachment.
>>
>> I have a piece of music arranged for Piano which I am practicing my
>> Lilypond engraving skills.
>>
>> The final bar (in the bass clef) is two half notes. The first half
>> note has a fingering of "5-3".
>>
>> How does one engrave that?
>>
>> Probably something obvious in the manual that I missed.
>>
>> Thanks in advance for your awesome assistance!
>>
>> Ken Wolcott
Re: Beam not breaking
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 8[ \break 8] 8
}
Is that expected output?
I've added this example to
https://gitlab.com/lilypond/lilypond/-/issues/3415
I've also posted a workaround there (but
I don't personally have the time to debug it
at the moment).
\version "2.23.6"
forceStemLength =
#(define-music-function (len) (number?)
(once
(propertyOverride
'(Stem after-line-breaking)
(lambda (grob)
(let ((beam (ly:grob-object grob 'beam)))
(ly:grob-property beam 'quantized-positions)
(ly:grob-set-property! grob 'length len))
{
\time 1/4
\override Beam.breakable = ##t
\override Beam.positions = #'(5 . 3)
c'8
\forceStemLength 16.5
8[ \break 8]
}
Best,
Jean
Re: How to implement a "5-3" fingering (Piano) (LP 2.22)
Hello Hans,
My bad, this must have been changed recently. Knute Snortum asked the same
thing in October, at which point the docs still had the old way. And when I
checked the stupid automatic language selector (why the heck do we have this?)
of course delegated me to the german documentation which is of course the only
one still using the old snippets.
So my remark becomes stupid, redunant and unnescessary.
Cheers,
Valentin
Am Samstag, 1. Jänner 2022, 11:05:41 CET schrieb Hans Aikema:
> Valentin,
>
> your remark confuses me.
> In what way is your suggested syntaxt different from what's in the docs?
>
> \relative {
> c''4-1 d-2 f\finger \markup \tied-lyric "4~3" c\finger "2 - 3"
> }
>
> I only see a few spaces which afaik only icrease readability, but apparently
> I overlook something.
>
> regards,
> Hans
>
> > On 1 Jan 2022, at 10:56, Valentin Petzel wrote:
> >
> > Hello Ken, hello David,
> >
> > the way given in the documentation is not particularly good, as this won't
> > produce a Fingering grob but a TextScript grob, which cannot be
> > positioned the same way.
> >
> > Much better would be to use
> >
> > e-\finger "5-3"
> > or
> > e-\finger\markup\tied-lyric "5~3"
> > or something.
> >
> > Cheers,
> > Valentin
> >
> > 01.01.2022 03:25:13 Kenneth Wolcott :
> >> HI David;
> >>
> >> Thank you. Read right past it, missing it entirely.
> >>
> >> Ken
> >>
> >>> On Fri, Dec 31, 2021 at 6:03 PM David M. Boothe, CAS
> >>> wrote:
> >>>
> >>> http://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff
> >>>
> >>> The second example under the heading "Fingering Instructions" gives you
> >>> a couple of options.
> >>>
> >>> dB
> >>>
> >>> On Fri, Dec 31, 2021, 8:51 PM Kenneth Wolcott
wrote:
> HI;
>
> How to implement a "5-3" fingering (Piano) (LP 2.22)
>
> See attachment.
>
> I have a piece of music arranged for Piano which I am practicing my
> Lilypond engraving skills.
>
> The final bar (in the bass clef) is two half notes. The first half
> note has a fingering of "5-3".
>
> How does one engrave that?
>
> Probably something obvious in the manual that I missed.
>
> Thanks in advance for your awesome assistance!
>
> Ken Wolcott
signature.asc
Description: This is a digitally signed message part.
Re: How to implement a "5-3" fingering (Piano) (LP 2.22)
Valentin,
your remark confuses me.
In what way is your suggested syntaxt different from what's in the docs?
\relative {
c''4-1 d-2 f\finger \markup \tied-lyric "4~3" c\finger "2 - 3"
}
I only see a few spaces which afaik only icrease readability, but apparently I
overlook something.
regards,
Hans
> On 1 Jan 2022, at 10:56, Valentin Petzel wrote:
>
> Hello Ken, hello David,
>
> the way given in the documentation is not particularly good, as this won't
> produce a Fingering grob but a TextScript grob, which cannot be positioned
> the same way.
>
> Much better would be to use
>
> e-\finger "5-3"
> or
> e-\finger\markup\tied-lyric "5~3"
> or something.
>
> Cheers,
> Valentin
>
> 01.01.2022 03:25:13 Kenneth Wolcott :
>
>> HI David;
>>
>> Thank you. Read right past it, missing it entirely.
>>
>> Ken
>>
>>> On Fri, Dec 31, 2021 at 6:03 PM David M. Boothe, CAS
>>> wrote:
>>>
>>> http://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff
>>>
>>> The second example under the heading "Fingering Instructions" gives you a
>>> couple of options.
>>>
>>> dB
>>>
>>> On Fri, Dec 31, 2021, 8:51 PM Kenneth Wolcott
>>> wrote:
HI;
How to implement a "5-3" fingering (Piano) (LP 2.22)
See attachment.
I have a piece of music arranged for Piano which I am practicing my
Lilypond engraving skills.
The final bar (in the bass clef) is two half notes. The first half
note has a fingering of "5-3".
How does one engrave that?
Probably something obvious in the manual that I missed.
Thanks in advance for your awesome assistance!
Ken Wolcott
>
Re: How to implement a "5-3" fingering (Piano) (LP 2.22)
Hello Ken, hello David, the way given in the documentation is not particularly good, as this won't produce a Fingering grob but a TextScript grob, which cannot be positioned the same way. Much better would be to use e-\finger "5-3" or e-\finger\markup\tied-lyric "5~3" or something. Cheers, Valentin 01.01.2022 03:25:13 Kenneth Wolcott : > HI David; > > Thank you. Read right past it, missing it entirely. > > Ken > > On Fri, Dec 31, 2021 at 6:03 PM David M. Boothe, CAS > wrote: >> >> http://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff >> >> The second example under the heading "Fingering Instructions" gives you a >> couple of options. >> >> dB >> >> On Fri, Dec 31, 2021, 8:51 PM Kenneth Wolcott >> wrote: >>> >>> HI; >>> >>> How to implement a "5-3" fingering (Piano) (LP 2.22) >>> >>> See attachment. >>> >>> I have a piece of music arranged for Piano which I am practicing my >>> Lilypond engraving skills. >>> >>> The final bar (in the bass clef) is two half notes. The first half >>> note has a fingering of "5-3". >>> >>> How does one engrave that? >>> >>> Probably something obvious in the manual that I missed. >>> >>> Thanks in advance for your awesome assistance! >>> >>> Ken Wolcott
