Syntax highlighting of a new grob name

I am trying to document \caesura in the Notation Reference. I have just made the docs starting from a clean build directory. I see that CaesuraScript is highlighted differently than other grob names in this text: \override Score.Script.color = ... \override Score.MultiMesaureRestScript.

Re: Syntax highlighting of a new grob name

Le 04/09/2022 à 21:15, Dan Eble a écrit : I am trying to document \caesura in the Notation Reference. I have just made the docs starting from a clean build directory. I see that CaesuraScript is highlighted differently than other grob names in this text: \override Score.Script.color = ..

Removing a snippet

Harm, The Contributor's Guide has sections on adding, editing, and renaming snippets. What should I do when I want to stop using a snippet in the Notation Reference? The one I have in mind now is "Inserting a caesura", though there might have been one in the past that I removed from the sourc

Re: Syntax highlighting of a new grob name

> I see that CaesuraScript is highlighted differently than other grob > names in this text: > > \override Score.Script.color = ... > \override Score.MultiMesaureRestScript.color = ... > \override Score.CaesuraScript.color = ... > > Can I do something to address this? TIA. Well, fi

Dropping "translation status"?

Hi all, when updating authors.texi for https://gitlab.com/lilypond/lilypond/-/merge_requests/1609 I noticed that I forgot to run translation-status for almost a year now. I've included it in the merge request, but then noticed that the file doc- translation-list.itexi wasn't updating since the doc

Re: Dropping "translation status"?

Le 04/09/2022 à 21:41, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Hi all, when updating authors.texi for https://gitlab.com/lilypond/lilypond/-/merge_requests/1609 I noticed that I forgot to run translation-status for almost a year now. I've included it in the merge request

Moving most initialization to .scm files

Hi, The long saga of https://gitlab.com/lilypond/lilypond/-/merge_requests/1510 continues ... The problem I am currently tackling is startup speed. When byte-compiling the code in .ly files, startup time increases from 0.3s to 0.8s, which is not quite acceptable. This is because the Guile byte

Re: Removing a snippet

Am So., 4. Sept. 2022 um 21:26 Uhr schrieb Dan Eble : > > Harm, > > The Contributor's Guide has sections on adding, editing, and renaming > snippets. What should I do when I want to stop using a snippet in the > Notation Reference? Well, short answer, adjust NR in Documentation/*/notation/expre

Re: Removing a snippet

On Sep 4, 2022, at 18:23, Thomas Morley wrote: > >> The Contributor's Guide has sections on adding, editing, and renaming >> snippets. What should I do when I want to stop using a snippet in the >> Notation Reference? > > Well, short answer, adjust NR in > Documentation/*/notation/expressive.

Re: Moving most initialization to .scm files

On Sep 4, 2022, at 16:38, Jean Abou Samra wrote: > > it will create conflicts with everyone's WIP local branches This is obviously unwelcome. I would need to read a lot before I would have a hope of speaking competently on this issue, and I'm very busy right now. — Dan