Re: Feedback wanted: syntax highlighting in the LilyPond documentation

2022-01-01 Thread Jean Abou Samra
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

Re: Feedback wanted: syntax highlighting in the LilyPond documentation

2022-01-01 Thread Calvin Ransom
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

Re: Make Grid take an edit id

2022-01-01 Thread Valentin Petzel
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

Re: Feedback wanted: syntax highlighting in the LilyPond documentation

2022-01-01 Thread 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

Feedback wanted: syntax highlighting in the LilyPond documentation

2022-01-01 Thread Jean Abou Samra
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:

Re: point-and-click default

2022-01-01 Thread Valentin Petzel
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

Re: Multiple grid lines in the same score

2022-01-01 Thread Valentin Petzel
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

Re: Multiple grid lines in the same score

2022-01-01 Thread 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

Re: point-and-click default

2022-01-01 Thread Wols Lists
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

Re: Multiple grid lines in the same score

2022-01-01 Thread Valentin Petzel
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

Re: Beam not breaking

2022-01-01 Thread Kieren MacMillan
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. :)

Multiple grid lines in the same score

2022-01-01 Thread 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.

Re: How to implement a "5-3" fingering (Piano) (LP 2.22)

2022-01-01 Thread Hans Aikema
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

Re: Beam not breaking

2022-01-01 Thread Jean Abou Samra
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)

Re: How to implement a "5-3" fingering (Piano) (LP 2.22)

2022-01-01 Thread Valentin Petzel
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

Re: How to implement a "5-3" fingering (Piano) (LP 2.22)

2022-01-01 Thread 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.

Re: How to implement a "5-3" fingering (Piano) (LP 2.22)

2022-01-01 Thread Valentin Petzel
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,