PATCHES - Countdown to July 11

2022-07-09 Thread Colin Campbell
Here is the current countdown list. The next countdown will begin July 11th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1459 Let -dembed-source-code include images and verbatim files - Jean Abou Samra

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Jean Abou Samra
> Le 9 juil. 2022 à 22:08, Dan Eble a écrit : > > Do you have any concern about other engravers might have acknowledged the > grobs that are about to be killed, which might have performed interesting > actions assuming that the grobs would continue to exist on one system or > another?

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread David Kastrup
Dan Eble writes: > On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: >> >> Instead of rearranging the translation process to let \fine abort >> translation, let translation run normally until the end. >> >> Then, ‘cut’ the result. > ... >> For layout output, there is already a battle-tested

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Dan Eble
On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: > > Instead of rearranging the translation process to let \fine abort > translation, let translation run normally until the end. > > Then, ‘cut’ the result. ... > For layout output, there is already a battle-tested algorithm, the one used > to

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Jean Abou Samra
> Le 9 juil. 2022 à 18:28, Dan Eble a écrit : > > Are you serious enough about this suggestion to propose syntax that you would > consider acceptably explicit and that could actually be implemented? To be clear, I’m not trying to find syntax acceptably explicit for me; this is not a

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Dan Eble
On Jul 9, 2022, at 11:56, Jean Abou Samra wrote: > > A third option: get out of this uncomfortable situation by > changing the syntax (it hasn't made it to a stable release > after all) so that which events are included and which > are not is fully explicit in the ly code. This idea is a bit

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Jean Abou Samra
Le 09/07/2022 à 17:38, David Kastrup a écrit : Unmatched events are a problem in MIDI. MIDI processors and sequencers working with files may to some degree try to repair such problems, partly because they need to do so when cutting and pasting regions as well. But you don't get guarantees.

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread David Kastrup
Jean Abou Samra writes: > Le 09/07/2022 à 16:31, Dan Eble a écrit : >> On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: >>> Then, ‘cut’ the result. For MIDI, that shouldn’t be too hard: while >>> outputting, just stop where \fine was used. >> For the events that are simultaneous with the \fine,

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Jean Abou Samra
Le 09/07/2022 à 16:22, Dan Eble a écrit : On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: For example, whether an item on the non-musical column at the point of \fine is included depends on whether its break-visibility makes it visible at EOL. The fine text itself will thus be included,

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Dan Eble
On Jul 9, 2022, at 10:38, Jean Abou Samra wrote: > > Le 09/07/2022 à 16:31, Dan Eble a écrit : >> On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: >>> Then, ‘cut’ the result. For MIDI, that shouldn’t be too hard: while >>> outputting, just stop where \fine was used. >> For the events that are

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Jean Abou Samra
Le 09/07/2022 à 16:31, Dan Eble a écrit : On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: Then, ‘cut’ the result. For MIDI, that shouldn’t be too hard: while outputting, just stop where \fine was used. For the events that are simultaneous with the \fine, would you emit them or not? If

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Dan Eble
On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: > > Then, ‘cut’ the result. For MIDI, that shouldn’t be too hard: while > outputting, just stop where \fine was used. For the events that are simultaneous with the \fine, would you emit them or not? If you would emit them, then you would emit

Re: \fine, pre-process-in-final-translation-timestep & co.

2022-07-09 Thread Dan Eble
On Jul 8, 2022, at 13:39, Jean Abou Samra wrote: > For example, whether an item on the non-musical column at the point of \fine > is included depends on whether its break-visibility makes it visible at EOL. > The fine text itself will thus be included, while a rehearsal mark won’t. > That is

Re: Does scripts/auxilar/make-regtest-pngs.sh function properly?

2022-07-09 Thread Han-Wen Nienhuys
On Sat, Jul 9, 2022 at 6:34 AM John Wheeler wrote: > I am trying to get the process documented in CG: 9.5 "Pixel-base regtest > comparison" to run. But, I am not able to get the command > > ./make-regtest-pngs.sh -j4 -o Why are you trying to run this script? David is adamant this script can't

Re: Does scripts/auxilar/make-regtest-pngs.sh function properly?

2022-07-09 Thread David Kastrup
John Wheeler writes: > I am trying to get the process documented in CG: 9.5 "Pixel-base > regtest comparison" to run.   But, I am not able to get the command > > ./make-regtest-pngs.sh -j4 -o > > to run without error.  Using git bisect points to commit > c85e9950a70d1765e4b9a637a737d873975dfb59,

Re: Does scripts/auxilar/make-regtest-pngs.sh function properly?

2022-07-09 Thread David Kastrup
John Wheeler writes: > I am trying to get the process documented in CG: 9.5 "Pixel-base > regtest comparison" to run.   But, I am not able to get the command > > ./make-regtest-pngs.sh -j4 -o > > to run without error.  Using git bisect points to commit > c85e9950a70d1765e4b9a637a737d873975dfb59,