Re: GUB: error running `make lilypond`

2016-07-25 Thread Federico Bruni
I made a new try and I see that the error is present also when running 'make bootstrap'. I've cleared target/linux-64/root/usr/lib and now I get this error: $ make bootstrap python bin/gub --platform=tools git calculating dependencies Checking for gcc ... /usr/bin/gcc must rebuild[tools]: system

Re: Gub failure

2016-07-25 Thread Masamichi Hosoda
>> Please use 5.x – 4.x is no longer supported. > > Or even better 6.x. I've created pull request for updating texinfo to 6.1. https://github.com/gperciva/gub/pull/25 In my GUB environment, the following commands are succeed. $ bin/gub tools::texinfo $ bin/gub linux-64::lilypond $ bin/gub linux

Re: vertical movement without anchors

2016-07-25 Thread Werner LEMBERG
>> That looks like the anchor point _is_ making a difference and that >> it is part of the skyline ultimately used for positioning in 2.18 >> (a skyline which fits beside the skyline of the opposing stem, >> resulting in a tighter adjustment). However, I don't see this >> observation explain the

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
Thomas Morley writes: > 2016-07-25 14:54 GMT+02:00 David Kastrup : > >> That looks like the anchor point _is_ making a difference and that it is >> part of the skyline ultimately used for positioning in 2.18 (a skyline >> which fits beside the skyline of the opposing stem, resulting in a >> tight

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Werner LEMBERG" > Cc: > Sent: Monday, July 25, 2016 2:07 PM > Subject: Re: vertical movement without anchors > > >> Werner LEMBERG writes: >> > When has this changed? Or maybe there are still situations

Re: vertical movement without anchors

2016-07-25 Thread Thomas Morley
2016-07-25 14:54 GMT+02:00 David Kastrup : > That looks like the anchor point _is_ making a difference and that it is > part of the skyline ultimately used for positioning in 2.18 (a skyline > which fits beside the skyline of the opposing stem, resulting in a > tighter adjustment). However, I don

Re: vertical movement without anchors

2016-07-25 Thread Phil Holmes
- Original Message - From: "David Kastrup" To: "Werner LEMBERG" Cc: Sent: Monday, July 25, 2016 2:07 PM Subject: Re: vertical movement without anchors Werner LEMBERG writes: When has this changed? Or maybe there are still situations where an anchor is needed, thus the example ha

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
Federico Bruni writes: > Il giorno lun 25 lug 2016 alle 15:07, David Kastrup ha > scritto: >> Do we >> have the docs for 2.17.18 and 2.17.19 for comparison? In other words, >> I'm a bit lazy. > > http://download.linuxaudio.org/lilypond/binaries/documentation/ No documentation for 2.17.*. The

Re: vertical movement without anchors

2016-07-25 Thread Federico Bruni
Il giorno lun 25 lug 2016 alle 15:07, David Kastrup ha scritto: Do we have the docs for 2.17.18 and 2.17.19 for comparison? In other words, I'm a bit lazy. http://download.linuxaudio.org/lilypond/binaries/documentation/ ___ lilypond-devel mailing

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
Werner LEMBERG writes: >>> When has this changed? Or maybe there are still situations where an >>> anchor is needed, thus the example has to be improved? >> >> The respective diff from 2.16 to 2.18 in scm/define-grobs.scm reads: >> [...] >> >> However, reverting all that does not appear to mak

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
Thomas Morley writes: > Just back from vacations, reading up the mails... > > I tested the code below with 2.16.2 and 2.19.44 and colored the ref-points. > Images attached. Up to now they are simple observations, have to think > about further implications... > > \relative d' { > \stemUp

Re: vertical movement without anchors

2016-07-25 Thread Thomas Morley
2016-07-25 14:29 GMT+02:00 Werner LEMBERG : > >>> When has this changed? Or maybe there are still situations where an >>> anchor is needed, thus the example has to be improved? >> >> The respective diff from 2.16 to 2.18 in scm/define-grobs.scm reads: >> [...] >> >> However, reverting all that doe

Re: vertical movement without anchors

2016-07-25 Thread Werner LEMBERG
>> When has this changed? Or maybe there are still situations where an >> anchor is needed, thus the example has to be improved? > > The respective diff from 2.16 to 2.18 in scm/define-grobs.scm reads: > [...] > > However, reverting all that does not appear to make a change (unless > I am doing

Re: vertical movement without anchors

2016-07-25 Thread David Kastrup
Werner LEMBERG writes: > The NR, section `Text alignment', says > > Vertical alignment is a bit more complex. As stated above, markup > objects can be moved as a whole; however, it is also possible to > move specific elements inside a markup block. In this case, the > element to be move

Re: [GSoC] Implement cross-voice dynamic spanners (issue 304160043 by starry...@gmail.com)

2016-07-25 Thread starrynte
Thank you very much for taking the time to review this! On 2016/07/25 10:01:52, dak wrote: The main problem I see with the current code is that it is ad-hoc and basically unmaintainable. Spanner_engraver is a class that really serves no clear purpose apart from carrying a few helper functio

vertical movement without anchors

2016-07-25 Thread Werner LEMBERG
The NR, section `Text alignment', says Vertical alignment is a bit more complex. As stated above, markup objects can be moved as a whole; however, it is also possible to move specific elements inside a markup block. In this case, the element to be moved needs to be preceded with an anch

Re: [GSoC] Implement cross-voice dynamic spanners (issue 304160043 by starry...@gmail.com)

2016-07-25 Thread dak
I've started going through with the code review here but at some point decided that I was missing the elephant in the room. So don't really bother with the code-related commment. The main problem I see with the current code is that it is ad-hoc and basically unmaintainable. Spanner_engraver is