Re: Puzzled at Git

2017-12-04 Thread Chris Yate
Hi David, I'm not sure, but I think you're specifying different ranges. Remember git rebase -i will be from your *current* branch to an ancestor, (and if it's not a direct ancestor, can include confusing stuff from more than one branch). Also not clear from the context what "origin" is. Usually

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

2017-11-05 Thread Chris Yate
Not within Frescobaldi... On 5 Nov 2017 11:38, "Phil Holmes" wrote: > - Original Message - From: "Chris Yate" > To: "Thomas Morley" > Cc: "David Kastrup" ; "lilypond-devel" < > lilypond-devel@gnu.org> > Sent: Fri

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

2017-11-03 Thread Chris Yate
n "assert", but is anyone planning to look at this issue? On Sat, 7 Jan 2017 at 18:50 Chris Yate wrote: > On Fri, 6 Jan 2017 at 12:41 Chris Yate wrote: > >> On Fri, 6 Jan 2017 at 12:23 Thomas Morley >> wrote: >> >> 2017-01-06 13:10 GMT+01:00 Chris Yate : &g

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

2017-01-07 Thread Chris Yate
On Fri, 6 Jan 2017 at 12:41 Chris Yate wrote: > On Fri, 6 Jan 2017 at 12:23 Thomas Morley > wrote: > > 2017-01-06 13:10 GMT+01:00 Chris Yate : > > > > > Curiously, this didn't fail with assertions. I've just upgraded to > 2.19.54, > > and the t

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

2017-01-06 Thread Chris Yate
On Fri, 6 Jan 2017 at 12:31 David Kastrup wrote: Chris Yate writes: > On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote: > >> >> Assertions should not be used when LilyPond has a sane way to continue: >> for that case, programming errors are more appropriate. The questi

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

2017-01-06 Thread Chris Yate
On Fri, 6 Jan 2017 at 12:23 Thomas Morley wrote: > 2017-01-06 13:10 GMT+01:00 Chris Yate : > > > > > Curiously, this didn't fail with assertions. I've just upgraded to > 2.19.54, > > and the test cases that crashed for me previously still crash :) > &g

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

2017-01-06 Thread Chris Yate
On Fri, 6 Jan 2017 at 10:23 Thomas Morley wrote: > 2017-01-04 16:01 GMT+01:00 Chris Yate : > > On Wed, 4 Jan 2017 at 14:25 Thomas Morley > wrote: > > > Well, it's odd. I'm not sure this is anything to do with > /overrideProperty. > > > > Referrin

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

2017-01-06 Thread Chris Yate
On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote: > > Assertions should not be used when LilyPond has a sane way to continue: > for that case, programming errors are more appropriate. The question is > whether this is the case here: I think we are also dealing with bad > output even when assertio

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

2017-01-04 Thread Chris Yate
On Wed, 4 Jan 2017 at 14:25 Thomas Morley wrote: > 2017-01-04 14:26 GMT+01:00 Chris Yate : > > > > On Wed, 4 Jan 2017 at 12:39 Thomas Morley > wrote: > >> > >> 2017-01-04 11:11 GMT+01:00 Chris Yate : > >> > >> > I'm not quite sur

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

2017-01-04 Thread Chris Yate
On Wed, 4 Jan 2017 at 12:39 Thomas Morley wrote: > 2017-01-04 11:11 GMT+01:00 Chris Yate : > > > I'm not quite sure what you want me to test, but, here's what I've tried. > [...] > > Hi Chris, > > sorry not been clear enough. > Many thanks for y

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

2017-01-04 Thread Chris Yate
On Tue, 3 Jan 2017 at 22:58 Thomas Morley wrote: > 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:

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

2017-01-03 Thread 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

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

2017-01-03 Thread 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 >

Re: LilyPond 2.20 release process

2017-01-03 Thread 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 numbe

Re: Unit testing

2016-11-01 Thread Chris Yate
On 1 Nov 2016 01:03, "Carl Sorensen" wrote: > > > > The only thing that I can think of for unit testing is to do the following: > > 1) For each file, define a set of regression tests that the file affects. > The set of regression tests should exercise all known functionality of the > files. > > 2)

Re: Unit testing

2016-10-29 Thread Chris Yate
On Sat, 29 Oct 2016 at 20:32 Urs Liska wrote: > > That's what I thought, and that's of course a good thing. But would it be > conceivable to actually start doing unit tests? One should probably not be > frightened by the issue that we won't be able to apply that backwardly, to > the existing code

Re: gub error

2016-10-24 Thread Chris Yate
On 11 Oct 2016 14:09, "John Karl" wrote: > > I'm trying to learn a little bit about how to do development work. My main impetus to this is the recent (and ongoing) problem with long compile times on OSX since v2.19.47. > Hi John, Did you get anywhere? I keep re-trying a gub build, but don't rea

Re: Help with GUB, or manual cross-compile

2016-10-05 Thread Chris Yate
On Sat, 1 Oct 2016 at 14:42 Masamichi Hosoda wrote: > >> Following up a conversation on the user list, as this might be a > >> better > >> place to ask... I think we've established that the only way to compile > >> for > >> Windows is to use GUB on Linux to cross-compile for mingw. > > > > Well I

Re: Help with GUB, or manual cross-compile

2016-10-01 Thread Chris Yate
On Sat, 1 Oct 2016 at 13:41 David Kastrup wrote: > If you can run this in a debugger in Windows, you could try giving a > backtrace. It might help enough for getting closer to the source of the > problem. > > -- > David Kastrup > David, Sorry for the separate replies. I can certainly run this

Re: Help with GUB, or manual cross-compile

2016-10-01 Thread Chris Yate
On Sat, 1 Oct 2016 at 13:41 David Kastrup wrote: > > > > The culprit is 2.19.21. > > Ah, that's likely to be not the real culprit but just the version where > assertions started to be enabled by default on Windows (and other) > builds. > > Of course, either warrant fixing if they occur. > > -- >

Re: Help with GUB, or manual cross-compile

2016-10-01 Thread Chris Yate
On Sat, 1 Oct 2016 at 12:50 Chris Yate wrote: > On Sat, 1 Oct 2016 at 12:27 Phil Holmes wrote: > > Have you narrowed the problem down to a specific new release? - e.g. it > happens in 2.19.32 but not 2.19.31? > > > Right. Very good point. > > I've started agai

Re: Help with GUB, or manual cross-compile

2016-10-01 Thread Chris Yate
On Sat, 1 Oct 2016 at 12:27 Phil Holmes wrote: > Have you narrowed the problem down to a specific new release? - e.g. it > happens in 2.19.32 but not 2.19.31? Right. Very good point. I've started again with Gub, with the platforms I don't care about commented out and have run "make bootstrap".

Help with GUB, or manual cross-compile

2016-10-01 Thread Chris Yate
Following up a conversation on the user list, as this might be a better place to ask... I think we've established that the only way to compile for Windows is to use GUB on Linux to cross-compile for mingw. Well, GUB barfs all the time here. I could start posting chunks of GUB log messages, but I do