Re: Custom MMR Range engraver problem under 2.19.83

2020-01-08 Thread Thomas Morley
Am Mo., 6. Jan. 2020 um 11:07 Uhr schrieb Thomas Morley
:
>
> Am Mo., 6. Jan. 2020 um 02:22 Uhr schrieb David Kastrup :

> >
> > 06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
> > commit 06be909202d2ced6e651e4420bc8068eafae023e
> > Author: Thomas Morley 
> > Date:   Sat May 26 23:45:55 2018 +0200
> >
> > Issue 5331 Let general-column deal reliable with empty args
> >
> > Previously an args-list of empty-stencils issued a programming error:
> >   Improbable offset for stencil: -inf staff space
> > This patch removes empty stencils from the args-list.
> > If args-list is empty, an empty stencil is returned.
> >
> > :04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998 
> > 2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm
> >
> >
> > --
> > David Kastrup
>
> Ok, thanks for bisecting.
> I'll rethink the problem. Not sure if I can propose anythink before
> Salzburg, though.

https://sourceforge.net/p/testlilyissues/issues/5655/
with patch

Cheers,
  Harm



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-06 Thread Thomas Morley
Am Mo., 6. Jan. 2020 um 02:22 Uhr schrieb David Kastrup :
>
> David Kastrup  writes:
>
> > Thomas Morley  writes:
> >
> >> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn 
> >> :
> >>>
> >>>
> >>>
> >>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> >>> > Hi all,
> >>> >
> >>> > I've been using the custom mmr-range-engraver (from this thread:
> >>> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> >>> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
> >>> > error messages at all. Just mmr bar numbers not displaying. Has anyone
> >>> > else experienced this?
> >>> >
> >>> > Craig
> >>>
> >>> Could you please give a minimal working example (or at least link to the
> >>> message containing a compilable code, not to the start of the thread)?
> >>>
> >>
> >> It's
> >> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
> >>
> >> A minimal for the problem:
> >>
> >> \markup
> >> \center-column {
> >>foo
> >>\translate #'(0 . 3)
> >>\with-dimensions #empty-interval #empty-interval
> >>bar
> >> }
> >>
> >> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> >> No clue what happens and why.
> >> Probably a bug, to tired to do further research, thoug.
> >
> > Bisecting.
>
> 06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
> commit 06be909202d2ced6e651e4420bc8068eafae023e
> Author: Thomas Morley 
> Date:   Sat May 26 23:45:55 2018 +0200
>
> Issue 5331 Let general-column deal reliable with empty args
>
> Previously an args-list of empty-stencils issued a programming error:
>   Improbable offset for stencil: -inf staff space
> This patch removes empty stencils from the args-list.
> If args-list is empty, an empty stencil is returned.
>
> :04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998 
> 2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm
>
>
> --
> David Kastrup

Ok, thanks for bisecting.
I'll rethink the problem. Not sure if I can propose anythink before
Salzburg, though.

Cheers,
  Harm



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread Craig Dabelstein
Thank you everyone.

Craig


On Mon, 6 Jan 2020 at 11:23, David Kastrup  wrote:

> David Kastrup  writes:
>
> > Thomas Morley  writes:
> >
> >> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn <
> lilyp...@maltemeyn.de>:
> >>>
> >>>
> >>>
> >>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> >>> > Hi all,
> >>> >
> >>> > I've been using the custom mmr-range-engraver (from this thread:
> >>> >
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> >>> > It was working perfectly under 2.19.82 but won't work under 2.19.83.
> No
> >>> > error messages at all. Just mmr bar numbers not displaying. Has
> anyone
> >>> > else experienced this?
> >>> >
> >>> > Craig
> >>>
> >>> Could you please give a minimal working example (or at least link to
> the
> >>> message containing a compilable code, not to the start of the thread)?
> >>>
> >>
> >> It's
> >> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
> >>
> >> A minimal for the problem:
> >>
> >> \markup
> >> \center-column {
> >>foo
> >>\translate #'(0 . 3)
> >>\with-dimensions #empty-interval #empty-interval
> >>bar
> >> }
> >>
> >> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> >> No clue what happens and why.
> >> Probably a bug, to tired to do further research, thoug.
> >
> > Bisecting.
>
> 06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
> commit 06be909202d2ced6e651e4420bc8068eafae023e
> Author: Thomas Morley 
> Date:   Sat May 26 23:45:55 2018 +0200
>
> Issue 5331 Let general-column deal reliable with empty args
>
> Previously an args-list of empty-stencils issued a programming error:
>   Improbable offset for stencil: -inf staff space
> This patch removes empty stencils from the args-list.
> If args-list is empty, an empty stencil is returned.
>
> :04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998
> 2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm
>
>
> --
> David Kastrup
>
>

-- 
Craig Dabelstein
Owner
Maxime's Music
M: 0404884173
A: 19 Twelfth Ave,  Kedron QLD 4031, Australia
W: concertbandmusicstore.com E:
cr...@concertbandmusicstore.com 






Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread David Kastrup
David Kastrup  writes:

> Thomas Morley  writes:
>
>> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>>>
>>>
>>>
>>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
>>> > Hi all,
>>> >
>>> > I've been using the custom mmr-range-engraver (from this thread:
>>> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
>>> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
>>> > error messages at all. Just mmr bar numbers not displaying. Has anyone
>>> > else experienced this?
>>> >
>>> > Craig
>>>
>>> Could you please give a minimal working example (or at least link to the
>>> message containing a compilable code, not to the start of the thread)?
>>>
>>
>> It's
>> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>>
>> A minimal for the problem:
>>
>> \markup
>> \center-column {
>>foo
>>\translate #'(0 . 3)
>>\with-dimensions #empty-interval #empty-interval
>>bar
>> }
>>
>> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
>> No clue what happens and why.
>> Probably a bug, to tired to do further research, thoug.
>
> Bisecting.

06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
commit 06be909202d2ced6e651e4420bc8068eafae023e
Author: Thomas Morley 
Date:   Sat May 26 23:45:55 2018 +0200

Issue 5331 Let general-column deal reliable with empty args

Previously an args-list of empty-stencils issued a programming error:
  Improbable offset for stencil: -inf staff space
This patch removes empty stencils from the args-list.
If args-list is empty, an empty stencil is returned.

:04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998 
2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm


-- 
David Kastrup



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread David Kastrup
Thomas Morley  writes:

> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>>
>>
>>
>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
>> > Hi all,
>> >
>> > I've been using the custom mmr-range-engraver (from this thread:
>> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
>> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
>> > error messages at all. Just mmr bar numbers not displaying. Has anyone
>> > else experienced this?
>> >
>> > Craig
>>
>> Could you please give a minimal working example (or at least link to the
>> message containing a compilable code, not to the start of the thread)?
>>
>
> It's
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>
> A minimal for the problem:
>
> \markup
> \center-column {
>foo
>\translate #'(0 . 3)
>\with-dimensions #empty-interval #empty-interval
>bar
> }
>
> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> No clue what happens and why.
> Probably a bug, to tired to do further research, thoug.

Bisecting.

-- 
David Kastrup



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread Thomas Morley
Am Mo., 6. Jan. 2020 um 01:09 Uhr schrieb Thomas Morley
:
>
> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
> >
> >
> >
> > Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> > > Hi all,
> > >
> > > I've been using the custom mmr-range-engraver (from this thread:
> > > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> > > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
> > > error messages at all. Just mmr bar numbers not displaying. Has anyone
> > > else experienced this?
> > >
> > > Craig
> >
> > Could you please give a minimal working example (or at least link to the
> > message containing a compilable code, not to the start of the thread)?
> >
>
> It's
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>
> A minimal for the problem:
>
> \markup
> \center-column {
>foo
>\translate #'(0 . 3)
>\with-dimensions #empty-interval #empty-interval
>bar
> }
>
> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> No clue what happens and why.
> Probably a bug, to tired to do further research, thoug.
>
> Anyway,
> Craig change formatMMRNumber to:
>
> formatMMRNumber =
> #(define-scheme-function (start stop)(integer? integer?)

Delete the line below, it's forgotten debugging code.

> (pretty-print (number->string (- stop start)))
> #{
>   \markup
> \column {
>\halign #0 #(number->string (- stop start))
> %   %% value found by try and error
>\translate-scaled #'(0 . -6.5)
>\with-dimensions #empty-interval #empty-interval
>\halign #0
>\normal-text
>\fontsize #-2
>\line {
>  #(number->string (1+  start))
>  " - "
>  #(number->string stop)
>}
> }
> #})
>
> and the functionality should be restored.
>
> Cheers,
>   Harm



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread Thomas Morley
Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>
>
>
> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> > Hi all,
> >
> > I've been using the custom mmr-range-engraver (from this thread:
> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
> > error messages at all. Just mmr bar numbers not displaying. Has anyone
> > else experienced this?
> >
> > Craig
>
> Could you please give a minimal working example (or at least link to the
> message containing a compilable code, not to the start of the thread)?
>

It's
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html

A minimal for the problem:

\markup
\center-column {
   foo
   \translate #'(0 . 3)
   \with-dimensions #empty-interval #empty-interval
   bar
}

With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
No clue what happens and why.
Probably a bug, to tired to do further research, thoug.

Anyway,
Craig change formatMMRNumber to:

formatMMRNumber =
#(define-scheme-function (start stop)(integer? integer?)
(pretty-print (number->string (- stop start)))
#{
  \markup
\column {
   \halign #0 #(number->string (- stop start))
%   %% value found by try and error
   \translate-scaled #'(0 . -6.5)
   \with-dimensions #empty-interval #empty-interval
   \halign #0
   \normal-text
   \fontsize #-2
   \line {
 #(number->string (1+  start))
 " - "
 #(number->string stop)
   }
}
#})

and the functionality should be restored.

Cheers,
  Harm



Re: Custom MMR Range engraver problem under 2.19.83

2020-01-05 Thread Malte Meyn




Am 06.01.20 um 00:02 schrieb Craig Dabelstein:

Hi all,

I've been using the custom mmr-range-engraver (from this thread: 
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html). 
It was working perfectly under 2.19.82 but won't work under 2.19.83. No 
error messages at all. Just mmr bar numbers not displaying. Has anyone 
else experienced this?


Craig


Could you please give a minimal working example (or at least link to the 
message containing a compilable code, not to the start of the thread)?