Re: Building issues (lilypond and docs)

[Alexander Kobel]

On 2016-12-30 22:04, Jay Anderson wrote:

In response to this thread:
https://lists.gnu.org/archive/html/lilypond-user/2016-12/msg00679.html
I'm attempting to build lilypond.


Hi Jay,

thanks for looking into this.


When building locally (an older version of mint linux) [...]


Sorry, I have no own experience with Mint, so I can only do some random 
guesswork. Which version of Mint are you using?



Cannot open /home/jay/programming/lilypond/build/mf/out/feta11.pfb
The requested file, feta11.pfb, does not exist
MergeFonts: Can't find font: feta11.pfb

Sure enough it looks like feta11.pfb wasn't built. What should I look
at to see why it wasn't built?


Can you call a `make out/feta11.pfb` in 
/home/jay/programming/lilypond/build/mf/? Maybe something is broken with 
the Metafont setup?


I guess you already checked the compilation requirements from

http://lilypond.org/doc/v2.18/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint 
and


http://lilypond.org/doc/v2.19/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint

AFAICS, the FontForge version that is used is recent enough (and I think 
it is even built with the --enable-double flag or its modern equivalent 
by default, and the package maintainers are unlikely to have changed 
this). Can you see anything suspicious when you manually perform the 
commands:



make[1]: Entering directory `/home/jay/programming/lilypond/build/mf'
/home/jay/programming/lilypond/build/scripts/build/out/gen-emmentaler-scripts
--dir=./out --design-size=11
cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe


The .genpe files are automatically generated by scripts. Does your Mint 
installation default to some recent Python2?
On Arch Linux, the following environment settings are used for building 
Lilypond packages:

  export PYTHON=python2
  export PYTHON_CONFIG=python2-config
  export GUILE=/usr/bin/guile1.8
  export GUILE_CONFIG=/usr/bin/guile-config1.8
where python2 is actually python2.7.


Moving on from that I tried using lilydev and it builds fine in the
virtual machine, but when attempting `make doc` it ran for days on the
learning manual before I killed it. I gave the virtual machine 2gb to
work with. I'm going to try upping that to 4gb before trying again. Is
there anything else to look at here?


Again, no idea, sorry. Building the documentation is a huge time-sink, 
but that's way more than expected...



Cheers,
Alexander

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: remove www from lilypond.org URL (issue 312190043 by fedel...@gmail.com)

[Matthewpatterson1881]

Do not write back to him I will just don't and for u I'm done
guess who the one who loves u with all my everything the one yea
me


https://codereview.appspot.com/312190043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyPond 2.20 release process

[Chris Yate]

On Sat, 31 Dec 2016 at 18:52 Trevor Daniels  wrote:

>
> Phil Holmes wrote Saturday, December 31, 2016 11:03 AM
>
>
> >I think there are a few bugs that need attention prior to stable release.
> > https://sourceforge.net/p/testlilyissues/issues/4975/ is one I'm aware
> of,
> > and there are a number of ones marked as critical.
>
> There are four bugs marked as critical regressions, see:
>
>
> https://sourceforge.net/p/testlilyissues/issues/search/?q=%28_type%3ACritical+OR+labels%3ARegression%29+AND+%28status%3ANew+OR+status%3AAccepted+OR+status%3AStarted%29
>
> It seems the sources of these bugs have been traced to patches submitted
> by devs who are no longer active:
>
> https://sourceforge.net/p/testlilyissues/issues/4807/
>
> Keith O'Hara
>
> https://sourceforge.net/p/testlilyissues/issues/4751/
>
> John Gourlay
>
> https://sourceforge.net/p/testlilyissues/issues/4182/
>
> Janek Warchol
>
> https://sourceforge.net/p/testlilyissues/issues/3778/
>
> Mike Solomon
>
> The patches are all large and quite far-reaching, so reversion is not an
> option.  Debugging has been attempted and (so far) abandoned.  So it is not
> clear what should be done.
>
> Discuss.
>
> Trevor


Hmm. No, agreed, not ready for release yet. This one prevents me using
Lilypond on Windows for anything other than pathologically small projects
(i.e. nothing that's actually useful).

https://sourceforge.net/p/testlilyissues/issues/4943/

We've traced the symptom of the crash down to Assertions being raised since
some point in 2.19, but AFAIK the cause is still unknown.

I've tried to create a symbols build so we can trace back / debug, but Gub
is simply not working for me. I don't really have the time to investigate
the Lilypond bug (which I have motivation to do), so I really don't have
time to investigate why Gub isn't working (which I really don't have
motivation for).

I've given up trying to make an instrumented build of Lilypond for
Windows/Mingw now, so if anybody else is able to create one for me that'd
be very welcome.

Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

possible fix for 5026 "\crossStaff mangles all grace note flags"?

[Thomas Morley]

Hi,

I had a look at
issue 5026 "\crossStaff mangles all grace note flags "
https://sourceforge.net/p/testlilyissues/issues/5026/

The code below checks additional for equal stem-durations.
If true connect stems, if not don't do so _and_ unset Flag.style.

Though, I'm not sure it's a proper fix.

I'd appreciate opinions/testings.


Thanks,
  Harm

\version "2.19.52"

#(define-public (my-Span_stem_engraver ctx)
  "Connect cross-staff stems to the stems above in the system"
  (let ((stems '()))
(make-engraver
 ;; Record all stems for the given moment
 (acknowledgers
  ((stem-interface trans grob source)
   (set! stems (cons grob stems
 ;; Process stems and reset the stem list to empty
 ((process-acknowledged trans)
  (let ((flags
  (flatten-list
(map
   (lambda (stem) (ly:grob-object stem 'flag))
   stems)))
(stem-durs
  (map
(lambda (stem) (ly:grob-property stem 'duration-log))
stems)))
  ;; condition to connect:
  ;; connect stems only if two or more present _and_ all are of same
  ;; duration and `stem-connectable?' is true (checked earlier)
  (if (and (<= 2 (length stems))
   (every (lambda (el) (= (car stem-durs) el)) stem-durs))
  ;; `make-stem-spans!' is not public, thus the @@-syntax
  ;; can be deleted if inserted in music-functions.scm
  ((@@ (lily) make-stem-spans!) ctx stems trans)
  ;; if the condition is false unset Flag.style
  (if (pair? flags)
  (ly:grob-set-property! (car flags) 'style '(
  (set! stems '()))

A = {
  c'8 \grace d'8 e'8 f' \grace g' fis' g'4 a'8 \noBeam b' c''8
}

B = {
  \voiceOne
  \autoBeamOff
  \crossStaff { c'8  \grace {  d'8 } e'8 \grace e'8 f' fis' g'8 a' b'4 }
  c''8
}

music = <<
  \new Staff
%% works only if patch for issue 4983 is present
%\with { \override Flag.stencil = #modern-straight-flag }
\A
  \new Staff
%% works only if patch for issue 4983 is present
%\with { \override Flag.stencil = #flat-flag }
\B
>>

\new PianoStaff
  \with {
\consists #Span_stem_engraver
instrumentName = "current"
  }
  \music

\new PianoStaff
  \with {
\consists #my-Span_stem_engraver
instrumentName = "proposed"
  }
  \music

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

[2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Thomas Morley]

This replies to
http://lists.gnu.org/archive/html/lilypond-devel/2017-01/msg00010.html

2017-01-03 12:23 GMT+01:00 Chris Yate :
>
> Hmm. No, agreed, not ready for release yet. This one prevents me using
> Lilypond on Windows for anything other than pathologically small projects
> (i.e. nothing that's actually useful).
>
> https://sourceforge.net/p/testlilyissues/issues/4943/
>
> We've traced the symptom of the crash down to Assertions being raised since
> some point in 2.19, but AFAIK the cause is still unknown.
>
> I've tried to create a symbols build so we can trace back / debug, but Gub
> is simply not working for me. I don't really have the time to investigate
> the Lilypond bug (which I have motivation to do), so I really don't have
> time to investigate why Gub isn't working (which I really don't have
> motivation for).
>
> I've given up trying to make an instrumented build of Lilypond for
> Windows/Mingw now, so if anybody else is able to create one for me that'd
> be very welcome.
>
> Chris_

Hi Chris,

I've just reread the Rietveld-discussion about
Issue 4169: Line and page breaking syntactic sugar
https://codereview.appspot.com/156400043/

I just wondered why autoLineBreaksOff/On was changed/extended by an
overrideProperty but _not_ autoPageBreaksOff/On.

So (completely shooting in the dark) may I ask you to test the following:

autoLineBreaksOff = {
  \overrideProperty Score.NonMusicalPaperColumn.line-break-permission ##f
  \override Score.NonMusicalPaperColumn.line-break-permission = ##f
}
autoLineBreaksOn = {
  \overrideProperty Score.NonMusicalPaperColumn.line-break-permission #'allow
  \override Score.NonMusicalPaperColumn.line-break-permission = #'allow
}
autoPageBreaksOff = {
  \overrideProperty Score.NonMusicalPaperColumn.page-break-permission ##f
  \override Score.NonMusicalPaperColumn.page-break-permission = ##f
}
autoPageBreaksOn = {
  \overrideProperty Score.NonMusicalPaperColumn.page-break-permission #'allow
  \override Score.NonMusicalPaperColumn.page-break-permission = #'allow
}

autoBreaksOff = { \autoLineBreaksOff \autoPageBreaksOff }
autoBreaksOn = { \autoLineBreaksOn \autoPageBreaksOn }


{ \repeat unfold 22 b2
  \autoPageBreaksOff
  %\autoBreaksOff
  \repeat unfold 320 b2
  \once \autoPageBreaksOn
  %\once \autoBreaksOn
  R1
  \repeat unfold 320 b2 }

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Chris Yate]

On Tue, 3 Jan 2017 at 16:03 Thomas Morley  wrote:

> This replies to
> http://lists.gnu.org/archive/html/lilypond-devel/2017-01/msg00010.html
>
> 2017-01-03 12:23 GMT+01:00 Chris Yate :
> >
> > Hmm. No, agreed, not ready for release yet. This one prevents me using
> > Lilypond on Windows for anything other than pathologically small projects
> > (i.e. nothing that's actually useful).
> >
> > https://sourceforge.net/p/testlilyissues/issues/4943/
> >
> > We've traced the symptom of the crash down to Assertions being raised
> since
> > some point in 2.19, but AFAIK the cause is still unknown.
> >
> > I've tried to create a symbols build so we can trace back / debug, but
> Gub
> > is simply not working for me. I don't really have the time to investigate
> > the Lilypond bug (which I have motivation to do), so I really don't have
> > time to investigate why Gub isn't working (which I really don't have
> > motivation for).
> >
> > I've given up trying to make an instrumented build of Lilypond for
> > Windows/Mingw now, so if anybody else is able to create one for me that'd
> > be very welcome.
> >
> > Chris_
>
> Hi Chris,
>
> I've just reread the Rietveld-discussion about
> Issue 4169: Line and page breaking syntactic sugar
> https://codereview.appspot.com/156400043/
>
> I just wondered why autoLineBreaksOff/On was changed/extended by an
> overrideProperty but _not_ autoPageBreaksOff/On.
>
> So (completely shooting in the dark) may I ask you to test the following:
>
> autoLineBreaksOff = {
>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission ##f
>   \override Score.NonMusicalPaperColumn.line-break-permission = ##f
> }
> autoLineBreaksOn = {
>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission
> #'allow
>   \override Score.NonMusicalPaperColumn.line-break-permission = #'allow
> }
> autoPageBreaksOff = {
>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission ##f
>   \override Score.NonMusicalPaperColumn.page-break-permission = ##f
> }
> autoPageBreaksOn = {
>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission
> #'allow
>   \override Score.NonMusicalPaperColumn.page-break-permission = #'allow
> }
>
> autoBreaksOff = { \autoLineBreaksOff \autoPageBreaksOff }
> autoBreaksOn = { \autoLineBreaksOn \autoPageBreaksOn }
>
>
> { \repeat unfold 22 b2
>   \autoPageBreaksOff
>   %\autoBreaksOff
>   \repeat unfold 320 b2
>   \once \autoPageBreaksOn
>   %\once \autoBreaksOn
>   R1
>   \repeat unfold 320 b2 }
>
> Cheers,
>   Harm
>

Hi Harm,

I've just run this in Windows (it's 8.1 here, I can test 10 later but I
doubt it'll be any different).

Output (pasted from the Log window in Frescobaldi):

Starting lilypond.exe 2.19.45 [Untitled]...

Processing `c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/
document.ly'

Parsing...

c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/document.ly:1
<0>: warning: no \version statement found, please add

\version "2.19.45"

for future compatibility

Interpreting
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328]

Preprocessing graphical objects...

Finding the ideal number of pages...

Fitting music on 1 or 2 pages...

This application has requested the Runtime to terminate it in an unusual
way.

Please contact the application's support team for more information.

Assertion failed!

Program: C:\Program Files (x86)\LilyPond 2.19.45\usr\bin\lilypond.exe

File:
/home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-breaking.cc,
Line 1180

Expression: ret <= cached_line_details_.size ()

Exited with return code 3.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Thomas Morley]

2017-01-03 17:10 GMT+01:00 Chris Yate :
>
>
> On Tue, 3 Jan 2017 at 16:03 Thomas Morley  wrote:
>>
>> This replies to
>> http://lists.gnu.org/archive/html/lilypond-devel/2017-01/msg00010.html
>>
>> 2017-01-03 12:23 GMT+01:00 Chris Yate :
>> >
>> > Hmm. No, agreed, not ready for release yet. This one prevents me using
>> > Lilypond on Windows for anything other than pathologically small
>> > projects
>> > (i.e. nothing that's actually useful).
>> >
>> > https://sourceforge.net/p/testlilyissues/issues/4943/
>> >
>> > We've traced the symptom of the crash down to Assertions being raised
>> > since
>> > some point in 2.19, but AFAIK the cause is still unknown.
>> >
>> > I've tried to create a symbols build so we can trace back / debug, but
>> > Gub
>> > is simply not working for me. I don't really have the time to
>> > investigate
>> > the Lilypond bug (which I have motivation to do), so I really don't have
>> > time to investigate why Gub isn't working (which I really don't have
>> > motivation for).
>> >
>> > I've given up trying to make an instrumented build of Lilypond for
>> > Windows/Mingw now, so if anybody else is able to create one for me
>> > that'd
>> > be very welcome.
>> >
>> > Chris_
>>
>> Hi Chris,
>>
>> I've just reread the Rietveld-discussion about
>> Issue 4169: Line and page breaking syntactic sugar
>> https://codereview.appspot.com/156400043/
>>
>> I just wondered why autoLineBreaksOff/On was changed/extended by an
>> overrideProperty but _not_ autoPageBreaksOff/On.
>>
>> So (completely shooting in the dark) may I ask you to test the following:
>>
>> autoLineBreaksOff = {
>>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission ##f
>>   \override Score.NonMusicalPaperColumn.line-break-permission = ##f
>> }
>> autoLineBreaksOn = {
>>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission
>> #'allow
>>   \override Score.NonMusicalPaperColumn.line-break-permission = #'allow
>> }
>> autoPageBreaksOff = {
>>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission ##f
>>   \override Score.NonMusicalPaperColumn.page-break-permission = ##f
>> }
>> autoPageBreaksOn = {
>>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission
>> #'allow
>>   \override Score.NonMusicalPaperColumn.page-break-permission = #'allow
>> }
>>
>> autoBreaksOff = { \autoLineBreaksOff \autoPageBreaksOff }
>> autoBreaksOn = { \autoLineBreaksOn \autoPageBreaksOn }
>>
>>
>> { \repeat unfold 22 b2
>>   \autoPageBreaksOff
>>   %\autoBreaksOff
>>   \repeat unfold 320 b2
>>   \once \autoPageBreaksOn
>>   %\once \autoBreaksOn
>>   R1
>>   \repeat unfold 320 b2 }
>>
>> Cheers,
>>   Harm
>
>
> Hi Harm,
>
> I've just run this in Windows (it's 8.1 here, I can test 10 later but I
> doubt it'll be any different).
>
> Output (pasted from the Log window in Frescobaldi):
>
> Starting lilypond.exe 2.19.45 [Untitled]...
>
> Processing
> `c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/document.ly'
>
> Parsing...
>
> c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/document.ly:1:
> warning: no \version statement found, please add
>
> \version "2.19.45"
>
> for future compatibility
>
> Interpreting
> music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328]
>
> Preprocessing graphical objects...
>
> Finding the ideal number of pages...
>
> Fitting music on 1 or 2 pages...
>
> This application has requested the Runtime to terminate it in an unusual
> way.
>
> Please contact the application's support team for more information.
>
> Assertion failed!
>
> Program: C:\Program Files (x86)\LilyPond 2.19.45\usr\bin\lilypond.exe
>
> File:
> /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-breaking.cc,
> Line 1180
>
> Expression: ret <= cached_line_details_.size ()
>
> Exited with return code 3.
>
>
>

So the shot in the dark failed.
Thanks for testing, though.

Do you have the same problems, while putting it in \layout and using
manual breaks? Like:

\layout {
  \autoBreaksOff
}

{ \repeat unfold 22 b2
  \repeat unfold 320 b2
  \break
  R1
  \repeat unfold 320 b2 }

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Chris Yate]

On Tue, 3 Jan 2017 at 16:23 Thomas Morley  wrote:

> 2017-01-03 17:10 GMT+01:00 Chris Yate :
> >
> >
> > On Tue, 3 Jan 2017 at 16:03 Thomas Morley 
> wrote:
> >>
> >> This replies to
> >> http://lists.gnu.org/archive/html/lilypond-devel/2017-01/msg00010.html
> >>
> >> 2017-01-03 12:23 GMT+01:00 Chris Yate :
> >> >
> >> > Hmm. No, agreed, not ready for release yet. This one prevents me using
> >> > Lilypond on Windows for anything other than pathologically small
> >> > projects
> >> > (i.e. nothing that's actually useful).
> >> >
> >> > https://sourceforge.net/p/testlilyissues/issues/4943/
> >> >
> >> > We've traced the symptom of the crash down to Assertions being raised
> >> > since
> >> > some point in 2.19, but AFAIK the cause is still unknown.
> >> >
> >> > I've tried to create a symbols build so we can trace back / debug, but
> >> > Gub
> >> > is simply not working for me. I don't really have the time to
> >> > investigate
> >> > the Lilypond bug (which I have motivation to do), so I really don't
> have
> >> > time to investigate why Gub isn't working (which I really don't have
> >> > motivation for).
> >> >
> >> > I've given up trying to make an instrumented build of Lilypond for
> >> > Windows/Mingw now, so if anybody else is able to create one for me
> >> > that'd
> >> > be very welcome.
> >> >
> >> > Chris_
> >>
> >> Hi Chris,
> >>
> >> I've just reread the Rietveld-discussion about
> >> Issue 4169: Line and page breaking syntactic sugar
> >> https://codereview.appspot.com/156400043/
> >>
> >> I just wondered why autoLineBreaksOff/On was changed/extended by an
> >> overrideProperty but _not_ autoPageBreaksOff/On.
> >>
> >> So (completely shooting in the dark) may I ask you to test the
> following:
> >>
> >> autoLineBreaksOff = {
> >>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission
> ##f
> >>   \override Score.NonMusicalPaperColumn.line-break-permission = ##f
> >> }
> >> autoLineBreaksOn = {
> >>   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission
> >> #'allow
> >>   \override Score.NonMusicalPaperColumn.line-break-permission = #'allow
> >> }
> >> autoPageBreaksOff = {
> >>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission
> ##f
> >>   \override Score.NonMusicalPaperColumn.page-break-permission = ##f
> >> }
> >> autoPageBreaksOn = {
> >>   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission
> >> #'allow
> >>   \override Score.NonMusicalPaperColumn.page-break-permission = #'allow
> >> }
> >>
> >> autoBreaksOff = { \autoLineBreaksOff \autoPageBreaksOff }
> >> autoBreaksOn = { \autoLineBreaksOn \autoPageBreaksOn }
> >>
> >>
> >> { \repeat unfold 22 b2
> >>   \autoPageBreaksOff
> >>   %\autoBreaksOff
> >>   \repeat unfold 320 b2
> >>   \once \autoPageBreaksOn
> >>   %\once \autoBreaksOn
> >>   R1
> >>   \repeat unfold 320 b2 }
> >>
> >> Cheers,
> >>   Harm
> >
> >
> > Hi Harm,
> >
> > I've just run this in Windows (it's 8.1 here, I can test 10 later but I
> > doubt it'll be any different).
> >
> > Output (pasted from the Log window in Frescobaldi):
> >
> > Starting lilypond.exe 2.19.45 [Untitled]...
> >
> > Processing
> > `c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/
> document.ly'
> >
> > Parsing...
> >
> > c:/users/cjyate/appdata/local/temp/frescobaldi-pv_nf1/tmpp6nmiv/
> document.ly:1:
> > warning: no \version statement found, please add
> >
> > \version "2.19.45"
> >
> > for future compatibility
> >
> > Interpreting
> >
> music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328]
> >
> > Preprocessing graphical objects...
> >
> > Finding the ideal number of pages...
> >
> > Fitting music on 1 or 2 pages...
> >
> > This application has requested the Runtime to terminate it in an unusual
> > way.
> >
> > Please contact the application's support team for more information.
> >
> > Assertion failed!
> >
> > Program: C:\Program Files (x86)\LilyPond 2.19.45\usr\bin\lilypond.exe
> >
> > File:
> >
> /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-breaking.cc,
> > Line 1180
> >
> > Expression: ret <= cached_line_details_.size ()
> >
> > Exited with return code 3.
> >
> >
> >
>
> So the shot in the dark failed.
> Thanks for testing, though.
>
> Do you have the same problems, while putting it in \layout and using
> manual breaks? Like:
>
> \layout {
>   \autoBreaksOff
> }
>
> { \repeat unfold 22 b2
>   \repeat unfold 320 b2
>   \break
>   R1
>   \repeat unfold 320 b2 }
>
> Cheers,
>   Harm
>


That example is OK, but I don't think the Layout makes any differece.

It seems it's the "autoPageBreaksOff" in particular that is a problem. A
few examples (not comprehensive):
--

This crashes:

{
  \autoPageBreaksOff
  \repeat unfold 22 b2
  \repeat unfold 320 b2

  R1
  \repeat unfold 320 b2
}

-
This cras

Re: LilyDev 5.0 released

[Federico Bruni]

Il giorno gio 29 dic 2016 alle 11:57, Thomas Morley 
 ha scritto:

 Though, I was surprised not to find the lilypond-git-repo. Did I
 overlook somthing?
 Anyway I cloned it manually.



 The first time you log in you should see a terminal popping up and 
asking for your name and email for git commits; then all the 
required repos are downloaded.

 The setup script is called by this file:

 
https://github.com/fedelibre/LilyDev/blob/master/config/includes.chroot/etc/skel/.config/autostart/lilydev.desktop


 Do you have this file within your home directory? 
~/.config/autostart/lilydev.desktop


 Is qterminal installed?


qterminal is installed and lilydev.desktop is present, though I've
never seen it executed.


I found out why it didn't work:

In ~/.config/autostart/lilydev.desktop you should:

1. replace ~ with $HOME. That is:
Exec=qterminal --workdir $HOME -e ./.lilydev-setup.sh

2. Remove this line:
Terminal=true

Otherwise you need the xterm package (which used to be automatically 
installed in previous versions, but it's not needed, as we have already 
qterminal), because it seems that if Terminal=true is set then the 
desktop file calls the xterm first and then executes the qterminal 
command.


I'm going to fix it immediately. Next release should work fine.


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[Federico Bruni]

Il giorno mer 28 dic 2016 alle 21:29, Graham Percival 
 ha scritto:

On Wed, Dec 28, 2016 at 06:24:48PM +0100, Federico Bruni wrote:

 The default should be httpredir:
  httpredir.debian.org

 Have you tried again? I hope that it's just a temporary network 
problem.


Yes, seems to have been temporary.  I tried it 3 times yesterday,
but now it's working.


Ok



I currently have an awkward problem with virtualbox on Ubuntu
16.04; it keeps on resizing the window one step smaller, until
it's something like 50 pixels high and 300 pixels wide.  This
doesn't happen if I maximize the window.  Very odd, and not unique
to lilydev; I see this when I virtualize ubuntu 16.04, but not
other operating systems.  Very odd.


I've just installed Virtual Box 5.1.10 from rpmfusion and it works fine.
You may try using a recent build, as suggested by James in this thread.




I've logged in, but it doesn't seem like like git-cl is installed?
The Contributor Guide says that it should be there:
http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl


Yes, a setup script was supposed to start at first login, but while 
upgrading LilyDev it stopped working. If you've followed the thread, 
this is now fixed.




In a similar note, could we get a Terminal icon on the taskbar?
Most people won't know that they can get an xterm by pressing
ctrl-alt-t.


Yes, I see that it's a matter of adding a few lines  to 
~/.config/lxqt/panel.conf (section [quicklaunch]).

I'll try to figure out what's the best way to add it in LilyDev.



In a related matter -- and please forgive me if we've discussed
this before -- have we considered distributing an exported OS?  In
the virtualbox GUI, this is called "Export Appliance", but it can
be done in a standard format so that (in theory) non-virtualbox
people can run it.  This would let people "get started" much
faster, and without the intimidation of installing Linux.  It
might also be easier to customize a bunch of things, such as
git-cl, and even putting a git clone of lilypond in there.


This is done already by a setup script, which you missed because 
LilyDev 5.0 was buggy.

But you can still run it manually:

cd ~
./.lilydev-setup.sh

In general, live-build allows to customize a bunch of things, see:
https://github.com/fedelibre/LilyDev/tree/master/config/includes.chroot/etc/skel


I realize that this would increase the filesize; it looks like
1.8 Gb for the exported appliance, compared to 1.1 GB for the
installer.


I remember that LilyPond developers were very concerned about the file 
size.
And the installation process is very easy. It might be made even 
easier, I think, by letting the debian-installer skip some optional 
configuration (such as the proxy settings).





(speaking of disk size, I see that the just-installed size is
3.1G.  What's pushing it so high?  texlive?  I poked around a bit,
but I couldn't find any packages that looks superfulous... maybe
I'm just out of date with how large installed software is these
days.  I must admit that I'm shocked to see that my desktop /usr/
is 8.5G !)


Yes, it's texlive. It pulls a lot of dependencies, including doc 
packages IIRC.
The system should be very basic, as live-build is configured to not 
install recommended packages.





___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[Federico Bruni]

Il giorno ven 23 dic 2016 alle 17:26, Paul  ha 
scritto:
Hi Federico, I double-checked and I do/did have the box checked to 
enable PAE.  I tried un-checking it and Virtual Box complained about 
it right away upon starting up the VM.


So when I get a chance I may try James' approach of using a newer 
version of Virtual Box, or else your approach with libvirt.  (No time 
at the moment though...)


Today I've installed Virtual Box 5.1.10 on Fedora from rpmfusion.
When I started the machine the first time I got an error about the 
kernel and I followed VB advice to run two commands as root user:


akmods
systemctl restart systemd-modules-load.service

Then it worked fine.
But Ubuntu doesn't use systemd, right?




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[Federico Bruni]

To everybody who installed LilyDev 5.0: do you see some icons missing 
in the menu? (e.g. under System Tools> qterminal)


It seems that the icon theme is not set by default. Probably a debian 
bug, but I've not investigated.
You can set it in the menu Preferences>LxQT settings>Appearance>Icons 
Theme and choose one of those listed (e.g. Adwaita).



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[David Kastrup]

Federico Bruni  writes:

> Il giorno ven 23 dic 2016 alle 17:26, Paul  ha
> scritto:
>> Hi Federico, I double-checked and I do/did have the box checked to
>> enable PAE.  I tried un-checking it and Virtual Box complained about
>> it right away upon starting up the VM.
>>
>> So when I get a chance I may try James' approach of using a newer
>> version of Virtual Box, or else your approach with libvirt.  (No
>> time at the moment though...)
>
> Today I've installed Virtual Box 5.1.10 on Fedora from rpmfusion.
> When I started the machine the first time I got an error about the
> kernel and I followed VB advice to run two commands as root user:
>
> akmods
> systemctl restart systemd-modules-load.service
>
> Then it worked fine.
> But Ubuntu doesn't use systemd, right?

Wrong.  They offer a boot alternative using upstart, but the default has
been changed to systemd.

Nice when it works, horrible to fix when it doesn't.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Thomas Morley]

2017-01-03 18:04 GMT+01:00 Chris Yate :
> On Tue, 3 Jan 2017 at 16:23 Thomas Morley  wrote:

>>
>> Do you have the same problems, while putting it in \layout and using
>> manual breaks? Like:
>>
>> \layout {
>>   \autoBreaksOff
>> }
>>
>> { \repeat unfold 22 b2
>>   \repeat unfold 320 b2
>>   \break
>>   R1
>>   \repeat unfold 320 b2 }
>>
> That example is OK, but I don't think the Layout makes any differece.
>
> It seems it's the "autoPageBreaksOff" in particular that is a problem. A few
> examples (not comprehensive):
[...]

Well, I have no windows at hand so I can't test all the examples.
But this one gives wrong output on Linux as well.
Only second system is printed at all !!

> This looks OK (though there's no breaks) but causes "Programming Error:
> bounds of spanner are invalid"
>
> {
>   \autoBreaksOff
>   \repeat unfold 22 b2
>   \repeat unfold 320 b2
> \break
>   R1
>   \repeat unfold 320 b2
> }

I've wrote some test-code, for testing with all stable versions since
2.12.3 and the new devel-versions.

%% snippet start

#(define testMusic
  (if (string-ci>? (cadr (string-split (lilypond-version) #\.)) "16")
;; 2.18. and higher
#{
   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission ##f
   \override Score.NonMusicalPaperColumn.line-break-permission = ##f
   \overrideProperty Score.NonMusicalPaperColumn.page-break-permission ##f
   \override Score.NonMusicalPaperColumn.page-break-permission = ##f

   \repeat unfold 320 b2
   \break
   R1
   \repeat unfold 320 b2

#}
#{
   \overrideProperty "Score.NonMusicalPaperColumn" #'line-break-permission ##f
   \override Score.NonMusicalPaperColumn #'line-break-permission = ##f
   \overrideProperty "Score.NonMusicalPaperColumn" #'page-break-permission ##f
   \override Score.NonMusicalPaperColumn #'page-break-permission = ##f

   \repeat unfold 320 b2
   \break
   R1
   \repeat unfold 320 b2
#}))

\new Staff \testMusic

%% snippet end

%%%

For all tested versions (2.12.3, 2.14.2, 2.16.2, 2.18.2, 2.19.52) I get
(1)
several instances of
programming error: bounds of spanner are invalid
continuing, cross fingers
(2)
first system is _never_ printed in pdf

%%%

If all instances of
\overrideProperty ...
in the snippet above are commented everything is always fine!!

%%%

That let me think something fundamental is broken with
overrideProperty for a very long time.
And as another shot in the dark: maybe the bug could be avoided by
deleting all overrideProperty-settings, i.e.

%% new defs start

autoLineBreaksOff =
  \override Score.NonMusicalPaperColumn.line-break-permission = ##f

autoLineBreaksOn =
  \override Score.NonMusicalPaperColumn.line-break-permission = #'allow

autoPageBreaksOff =
  \override Score.NonMusicalPaperColumn.page-break-permission = ##f

autoPageBreaksOn =
  \override Score.NonMusicalPaperColumn.page-break-permission = #'allow

autoBreaksOff = { \autoLineBreaksOff \autoPageBreaksOff }

autoBreaksOn = { \autoLineBreaksOn \autoPageBreaksOn }

%% new defs end

This will ofcourse limit the possible use-cases:
As of the discussion on Rietveld it was intended to use
autoBreaksOff/On prepended with \once in mid-music. This will likely
not work in all cases anymore.

Anyway,
Chris, may I ask you to test with definitions above?

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

5027: NR example with bad engraving practice

[Simon Albrecht]

Hello,

I know this is a bit on the edge of being too keen on my part, but I 
don’t consider this controversial at all from my engraving experience 
and knowledge of current best practice.


NR 1.2.1.d 
 
correctly says that ‘Ties should also be used when note values cross 
larger subdivisions of the measure’. However the example highlights (in 
4/4 time)


8 8~ 2 r4

as good example, where the half note still crosses the largest 
subdivision in the measure.


8 4.~ 4 r4

is clearly preferable.

I created a ticket 
, but since I 
don’t have access to my Google account right now, I can’t upload the 
patch to Rietveld myself; it’s attached to the issue and to this e-mail.


Best, Simon

>From a57e7005dab3c2b119827a2658eaf5025e7ff2ca Mon Sep 17 00:00:00 2001
From: Simon Albrecht 
Date: Tue, 3 Jan 2017 23:41:00 +0100
Subject: [PATCH] NR 1.2.1.d: Split note correctly

In 4/4 time, a note crossing the middle of the bar should be
split at the middle of the bar.  The current example displays
bad engraving practice.
---
 Documentation/notation/rhythms.itely | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/notation/rhythms.itely b/Documentation/notation/rhythms.itely
index 2df6cba..640a6c8 100644
--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
@@ -443,8 +443,9 @@ used when note values cross larger subdivisions of the measure:
 
 @lilypond[verbatim,quote]
 \relative {
-  r8 c'~ 2 r4 |
-  r8^"not" c2~ 8 r4
+  r8 c'4.~ 4 r4 |
+  r8^"not" c2~ 8 r4 |
+  r8^"neither" c~ 2 r4
 }
 @end lilypond
 
-- 
1.9.1

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

[thomasmorley65]

Reviewers: ,

Message:
Please review
(I shepherd this for Simon, as long as he has problems with his google
account)

Description:
NR 1.2.1.d: Split note correctly

In 4/4 time, a note crossing the middle of the bar should be
split at the middle of the bar.  The current example displays
bad engraving practice.

Please review this at https://codereview.appspot.com/319940043/

Affected files (+3, -2 lines):
  M Documentation/notation/rhythms.itely


Index: Documentation/notation/rhythms.itely
diff --git a/Documentation/notation/rhythms.itely  
b/Documentation/notation/rhythms.itely
index  
2df6cbaee7ec22e39e9072fdeba2f2b0b09656db..640a6c8ed68fad020a2d460808a35083aa476e88  
100644

--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
@@ -443,8 +443,9 @@ used when note values cross larger subdivisions of the  
measure:


 @lilypond[verbatim,quote]
 \relative {
-  r8 c'~ 2 r4 |
-  r8^"not" c2~ 8 r4
+  r8 c'4.~ 4 r4 |
+  r8^"not" c2~ 8 r4 |
+  r8^"neither" c~ 2 r4
 }
 @end lilypond




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

[Simon Albrecht]

On 04.01.2017 00:14, thomasmorle...@gmail.com wrote:

(I shepherd this for Simon, as long as he has problems with his google
account) 


Thanks.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

[tdanielsmusic]

LGTM

Trevor

https://codereview.appspot.com/319940043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel