Regtests cleanup: fix texidoc strings (issue 571950043 by v.villen...@gmail.com)

2020-04-03 Thread lemzwerg--- via Discussions on LilyPond development
LGTM, thanks! https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly File input/regression/auto-beam-exceptions.ly (right): https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly#newcode7 input/regression/auto-be

Cannot make check from current master (with no patches applied)

2020-04-03 Thread pkx166h
Hello, I cannot run a make check from current master. --snip.. no source for input/regression/midi/out-test/sequence-name-scoping-1.midi no source for input/regression/midi/out-test/sequence-name-scoping-2.midi no source for input/regression/midi/out-test/sequence-name-scoping-3.midi no source

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread David Kastrup
pkx166h writes: > Hello, > > I cannot run a make check from current master. > > --snip.. > > no source for input/regression/midi/out-test/sequence-name-scoping-1.midi > no source for input/regression/midi/out-test/sequence-name-scoping-2.midi > no source for input/regression/midi/out-test/sequenc

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread David Kastrup
David Kastrup writes: > pkx166h writes: > >> Hello, >> >> I cannot run a make check from current master. >> >> --snip.. >> >> no source for input/regression/midi/out-test/sequence-name-scoping-1.midi >> no source for input/regression/midi/out-test/sequence-name-scoping-2.midi >> no source for in

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread David Kastrup
David Kastrup writes: > David Kastrup writes: > >> pkx166h writes: >> >>> Hello, >>> >>> I cannot run a make check from current master. >>> >>> --snip.. >>> >>> no source for input/regression/midi/out-test/sequence-name-scoping-1.midi >>> no source for input/regression/midi/out-test/sequence-na

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread pkx166h
Hello, On 03/04/2020 16:03, David Kastrup wrote: David Kastrup writes: David Kastrup writes: pkx166h writes: Hello, I cannot run a make check from current master. --snip.. no source for input/regression/midi/out-test/sequence-name-scoping-1.midi no source for input/regression/midi/ou

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread Valentin Villenave
On 4/3/20, David Kastrup wrote: > Anybody have an idea whose Patchy pushed the following: > commit f5f907599ce88d3d610483fa42fa78be12f53d2e Uh, I did push it onto staging after the usual review process. Could that really be what broke some stuff? It’s a fairly simple documentation edit… (Unlik

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread David Kastrup
Valentin Villenave writes: > On 4/3/20, David Kastrup wrote: >> Anybody have an idea whose Patchy pushed the following: >> commit f5f907599ce88d3d610483fa42fa78be12f53d2e > > Uh, I did push it onto staging after the usual review process. Could > that really be what broke some stuff? It’s a fai

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread David Kastrup
David Kastrup writes: > Valentin Villenave writes: > >> On 4/3/20, David Kastrup wrote: >>> Anybody have an idea whose Patchy pushed the following: >>> commit f5f907599ce88d3d610483fa42fa78be12f53d2e >> >> Uh, I did push it onto staging after the usual review process. Could >> that really be w

Re: Cannot make check from current master (with no patches applied)

2020-04-03 Thread Han-Wen Nienhuys
On Fri, Apr 3, 2020 at 4:41 PM pkx166h wrote: > > Hello, > > I cannot run a make check from current master. http://codereview.appspot.com/563810043 -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

2020-04-03 Thread dak
Is this likely related to the problems in `make check` that James currently experiences? https://codereview.appspot.com/563810043/

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

2020-04-03 Thread hanwenn
Reviewers: dak, Message: On 2020/04/03 22:00:02, dak wrote: > Is this likely related to the problems in `make check` that James currently > experiences? Yes. Unfortunately, the default encoding depends on the environment " In text mode, if encoding is not specified the encoding used is pla

Re: Remove all uses of markup macro from scm/*.scm (issue 575930043 by d...@gnu.org)

2020-04-03 Thread hanwenn
note that this still doesn't fix the next error message for compilation which is fatal error: Not a markup command: line which is triggered by the *definition* of the markup macro: (defmacro*-public markup (#:rest body) .. (car (compile-all-markup-expressions `(#:line ,body the markup c

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

2020-04-03 Thread dak
https://codereview.appspot.com/563810043/diff/545810044/scripts/build/output-distance.py File scripts/build/output-distance.py (right): https://codereview.appspot.com/563810043/diff/545810044/scripts/build/output-distance.py#newcode1328 scripts/build/output-distance.py:1328: system (u'echo HEAD

Re: Remove all uses of markup macro from scm/*.scm (issue 575930043 by d...@gnu.org)

2020-04-03 Thread dak
On 2020/04/03 22:22:31, hanwenn wrote: > note that this still doesn't fix the next error message for compilation which is > > > > fatal error: Not a markup command: line > > which is triggered by the *definition* of the markup macro: > > (defmacro*-public markup (#:rest body) > .. > (car (co