Re: Let repeatTie work inside of event-chord (issue 335910043 by thomasmorle...@gmail.com)

On 2017/10/22 20:01:03, dak wrote: On 2017/10/22 19:26:12, benko.pal wrote: > if it's really the same, can't it be used without copying? or if separate > classes are absolutely needed, can't the common part be gathered in a common > base class? You mean, like with Slur/PhrasingSlur?

Re: Let repeatTie work inside of event-chord (issue 335910043 by thomasmorle...@gmail.com)

On 2017/10/22 19:26:12, benko.pal wrote: if it's really the same, can't it be used without copying? or if separate classes are absolutely needed, can't the common part be gathered in a common base class? You mean, like with Slur/PhrasingSlur? Well, for one thing, then someone needs to

Re: Let repeatTie work inside of event-chord (issue 335910043 by thomasmorle...@gmail.com)

if it's really the same, can't it be used without copying? or if separate classes are absolutely needed, can't the common part be gathered in a common base class? https://codereview.appspot.com/335910043/ ___ lilypond-devel mailing list

Re: obfuscated build-log

2017-10-22 14:52 GMT+02:00 Phil Holmes : > - Original Message - From: "Thomas Morley" > > To: "lilypond-devel" > Sent: Sunday, October 22, 2017 9:16 AM > Subject: obfuscated build-log > > > >> Hi, >> >> I just failed

Re: obfuscated build-log

- Original Message - From: "Thomas Morley" To: "lilypond-devel" Sent: Sunday, October 22, 2017 9:16 AM Subject: obfuscated build-log Hi, I just failed to build lilypond, because I forgot to rerun configure, etc after checking and

obfuscated build-log

Hi, I just failed to build lilypond, because I forgot to rerun configure, etc after checking and building an experimental branch. While the mistake is obvious, the log obfuscates it by adding a wagonload of output after the error is stated. I would have expected to see the error last. Is it