Re: build problems
On Jan 11, 2022, at 17:40, Dan Eble wrote: > >> >> Any hint how to proceed? Thanks in advance! > > Can you provide the (Whoops! Premature send.) Can you provide the commands one would use to reproduce the issue? — Dan
Re: build problems
On Jan 11, 2022, at 11:37, Werner Arnhold wrote: > > Hello, > > I tried to build the program and ended up with this message: > > Traceback (most recent call last): > File "/usr/local/software/lilypond/build/../scripts/lilypond- > book.py", line 72, in >import book_base > ModuleNotFoundError: No module named 'book_base' > make[1]: *** [/usr/local/software/lilypond/build/.././make/lilypond- > book-rules.make:6: out/en/changes.texi] Error 1 > make: *** > [/usr/local/software/lilypond/build/../stepmake/stepmake/generic- > targets.make:6: all] Fehler 2 > > I tried > > find .. -name "book_base*" > > and got > > ../build/python/out/book_base.pyc.dummy > ../build/python/out/__pycache__/book_base.cpython-37.pyc > ../python/book_base_test.py > ../python/book_base.py > > Any hint how to proceed? Thanks in advance! Can you provide the
Re: Planning for 2.22.2
On Mon, Jan 10, 2022 at 8:36 PM Jonas Hahnfeld via Discussions on LilyPond development wrote: > > Hi all, > > there's a number of fixes stacking up in stable/2.22 (at least after I > processed the patches that I marked for backporting in the past months) > and I'd like to tentatively plan for the next bug fix release 2.22.2 > some time in February. We could collect some bonus points by going for > the 22nd, but we'll see if and how that works out It would be awesome to release 2.22.2 on 22/2/2022 ! :) thanks for driving this! > So please let me know if you have anything that you think would be good > to include and that I haven't backported yet. I hope wrote a comment on > all MRs that I cherry-picked commits from, and changed the milestones > of the corresponding issues, if there is one... I had a quick look at my recent changes, but you have the important ones already. > I would have liked to include some more balloon fixes, but already > https://gitlab.com/lilypond/lilypond/-/merge_requests/1071 doesn't > produce the expected results (no footnote on the MultiMeasureRestNumber > and \after is not available in 2.22 at all), and the fix from > https://gitlab.com/lilypond/lilypond/-/merge_requests/1077 doesn't seem > to work either. I suspect they require the sticky grob infrastructure, > so I've given up on them unless somebody (Jean?) can tell me that which > prerequisite to pick first. I'd stick to infrastructure fixes (eg. avoid crashes), and avoid cherry-picking changes to the formatting engine -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: Discussion: Improved Scheme interface for finding contexts
Le 11/01/2022 à 23:12, Dan Eble a écrit :
On Jan 11, 2022, at 11:35, Jean Abou Samra wrote:
(ly:context-find-id context)
(No direction: there cannot be two contexts with the
same ID, can there? I cannot imagine
Allow me:
<<
\new PianoStaff <<
\new Staff = "RH" ...
\new Staff = "LH" ...
>>
\new PianoStaff <<
\new Staff = "RH" ...
\new Staff = "LH" ...
>>
Another example is a user who uses \partCombine in more than one Staff. There
will be multiple Voices with the same ID because they are baked into the
implementation:
#{ \context Staff <<
\context Voice = "one" \with #one-context-settings { #skip }
\context Voice = "two" \with #two-context-settings { #skip }
\context Voice = "shared" \with #shared-context-settings { #skip }
\context Voice = "solo" { #skip }
\context NullVoice = "null" { #skip }
#pc-music
#(make-part-combine-marks
default-part-combine-mark-state-machine split-list)
>> #} ))
Ah, ok. Seems like I misunderstood the whole
concept of having context IDs...
Thanks for correcting me.
Regards,
Jean
Re: Discussion: Improved Scheme interface for finding contexts
On Jan 11, 2022, at 11:35, Jean Abou Samra wrote:
>
> (ly:context-find-id context)
>(No direction: there cannot be two contexts with the
>same ID, can there? I cannot imagine
Allow me:
<<
\new PianoStaff <<
\new Staff = "RH" ...
\new Staff = "LH" ...
>>
\new PianoStaff <<
\new Staff = "RH" ...
\new Staff = "LH" ...
>>
>>
Another example is a user who uses \partCombine in more than one Staff. There
will be multiple Voices with the same ID because they are baked into the
implementation:
#{ \context Staff <<
\context Voice = "one" \with #one-context-settings { #skip }
\context Voice = "two" \with #two-context-settings { #skip }
\context Voice = "shared" \with #shared-context-settings { #skip }
\context Voice = "solo" { #skip }
\context NullVoice = "null" { #skip }
#pc-music
#(make-part-combine-marks
default-part-combine-mark-state-machine split-list)
>> #} ))
—
Dan
build problems
Hello, I tried to build the program and ended up with this message: Traceback (most recent call last): File "/usr/local/software/lilypond/build/../scripts/lilypond- book.py", line 72, in import book_base ModuleNotFoundError: No module named 'book_base' make[1]: *** [/usr/local/software/lilypond/build/.././make/lilypond- book-rules.make:6: out/en/changes.texi] Error 1 make: *** [/usr/local/software/lilypond/build/../stepmake/stepmake/generic- targets.make:6: all] Fehler 2 I tried find .. -name "book_base*" and got ../build/python/out/book_base.pyc.dummy ../build/python/out/__pycache__/book_base.cpython-37.pyc ../python/book_base_test.py ../python/book_base.py Any hint how to proceed? Thanks in advance! Werner
Re: Discussion: Improved Scheme interface for finding contexts
Le 09/01/2022 à 12:21, Valentin Petzel a écrit : Hello, https://gitlab.com/lilypond/lilypond/-/merge_requests/1126 I’ve proposed some changes to ly:context-find to allow better music function support for talking to other contexts. Feel free to throw in your opinion about the matter and the interface. Well, if you are looking for opinions, here is mine: I prefer interfaces with several functions each serving a specific purposes over interfaces with one function serving all purposes. I find this to make code generally easier to grasp, disambiguate the interpretation of arguments and save remembering the order and meaning of each argument (though you could make them named with #: keywords if you accept to parse the argument list yourself; I don't think any equivalent to define*/lambda* exists on the C++ level). So my take would be along the lines of: (ly:context-find context name) (as existing) (ly:context-find-below context name) (ly:context-find-id context) (No direction: there cannot be two contexts with the same ID, can there? I cannot imagine a use case for restricting the search to parents or children.) (ly:make-context context name) (Creating a context below.) As you can see, cases that are unlikely to be useful are not provided: finding by name everywhere, finding by ID above or below, creating above or anywhere. (Your mileage may vary.) My 2 cents, and having only skimmed the code due to lack of time. HTH Jean
PATCHES - Countdown for January 11th
Hello, Here is the current patch countdown list. The next countdown is scheduled for January 13th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1116 articulate.ly: Silence Guile 2 complaint - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1116 !1112 NR: Cover recent \repeat changes - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/1112 ! Doc-CG: add warning about Texinfo markup on GitLab - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/ !1109 texi2html: Never use 'section ' prefix in links. - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/1109 !1108 Bump libpng to 1.6.0 - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1108 !1104 font-name-add-files: embed fonts unconditionally in test output - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1104 !1101 Doc-NR: add some more info about horizontal spacing - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1101 !1100 Doc-NR: improve formatting of MIDI instrument list - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1100 !1091 Doc-CG: update "Administrative policies" and "Issues" - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1091 Countdown: !1128 Build mo files as po/out/LANG/LC_MESSAGES/lilypond.mo - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1128 !1125 Doc: update instructions for translators - Federico Bruni https://gitlab.com/lilypond/lilypond/-/merge_requests/1125 !1124 Fix invisible bar lines at beginning of line - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/1124 !1122 Doc-IR: also autodocument macros - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1122 !1121 separation-item.cc: Don't copy std::vector - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1121 !1120 Volta_specced_music_iterator: protect start/stop event against GC - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1120 !1119 Crash if umsmob sees a freed smob - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1119 !1118 Build with cairo on CI - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1118 !1115 Web: mention https://extending-lilypond.readthedocs.io - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1115 !1114 Doc-IR: improve autogenerated backend documentation for grob classes - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1114 !1106 simple-spacer: make solve() a const method - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1106 !1102 Improve skyline debugging experience - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1102 !1093 Doc-NR: overhaul "Changing defaults" (part 1) - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1093 Review: !1129 Do not shift BreathingSign at \bar "" - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/1129 !1126 Draft:Improve the scheme interface for finding contexts. - Valentin Petzel https://gitlab.com/lilypond/lilypond/-/merge_requests/1126 New: No patches in New at this time. Waiting: !1127 Rework markup->string - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1127 !1107 simple-spacer: compute rod_force exactly - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/1107 !913 release: binaries with cairo - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/913 -- Regards James
Re: Texinfo error: need help for debugging
On Tue, Jan 11 2022 at 05:14:37 +, Werner LEMBERG
wrote:
AFAIK, the problematic error message is the following:
.../Documentation/out-www/it/it/usage/updating.texi:14: This command
can appear only outside of any environment, not in environment
@raggedright.
This means that somewhere before line 14 of `updating.texi` – most
certainly in another file – the `raggedright` environment wasn't
properly closed.
We don't use the `raggedright` environment directly. Instead, we use
the `@raggedRight` and `@endRaggedRight` macros.
Note that `@endRaggedRight` isn't normally used directly either;
instead, they are part of the `@endmorerefs` and `@endpredefined`
macros.
My conclusion: In a file included before `updating.texi`, you are
missing either `@endmorerefs` or `@endpredefined`.
You guessed it right.
I thought texinfo would have pointed me to the right file.
Here's the fix:
$ git diff
diff --git a/Documentation/it/usage/running.itely
b/Documentation/it/usage/running.itely
index 1c6e1f6e62..518e62a1c7 100644
--- a/Documentation/it/usage/running.itely
+++ b/Documentation/it/usage/running.itely
@@ -1608,3 +1608,4 @@ naturale (quando le note di @code{\voiceThree}
sono più alte di quelle di
@rlearning{Esempio musicale},
@ruser{Polifonia su un solo rigo},
@ruser{Risoluzione delle collisioni}.
+@endmorerefs
Thanks
Federico
Re: Texinfo error: need help for debugging
Werner LEMBERG writes: > Hello Federico, > >> I'm testing a translation patch and I cannot understand which >> mistake is causing the following error: > > AFAIK, the problematic error message is the following: > >> .../Documentation/out-www/it/it/usage/updating.texi:14: This command >> can appear only outside of any environment, not in environment >> @raggedright. > > This means that somewhere before line 14 of `updating.texi` – most > certainly in another file – the `raggedright` environment wasn't > properly closed. > > We don't use the `raggedright` environment directly. Instead, we use > the `@raggedRight` and `@endRaggedRight` macros. > > Note that `@endRaggedRight` isn't normally used directly either; > instead, they are part of the `@endmorerefs` and `@endpredefined` > macros. > > My conclusion: In a file included before `updating.texi`, you are > missing either `@endmorerefs` or `@endpredefined`. Or it means that @chapter sets its argument in @raggedright (possibly in a table-of-contents diversion) and does not allow @command to be used inside of its argument. -- David Kastrup
