Issue 4176: Add regtests for numbered and single-digit time signature styles (issue 162300043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread nine . fierce . ballads
Reviewers: , Description: Add regtests for numbered and single-digit time signature styles https://code.google.com/p/lilypond/issues/detail?id=4176 Please review this at https://codereview.appspot.com/162300043/ Affected files (+38, -0 lines): A input/regression/time-signature-numbered.ly A

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread Joram
Hi Dan, Am 26.10.2014 um 22:19 schrieb Dan Eble: On Oct 26, 2014, at 16:21 , Joram wrote: The way I have been looking at it, c represents quadruple meter and ¢ represents duple. This is an interpretation I guessed from 4/4=c and 2/2=¢, too. But I don’t think it is correct from the above

Re: Doc: NR section 3.5.x MIDI file creation tidy up (issue 120480043 by pkx1...@gmail.com)

2014-10-26 Thread tdanielsmusic
I still have a couple of difficulties with this. It is very difficult to see what articulations are represented in basic Midi output and what are not. Clear lists are needed, ideally quite early rather than buried in the detail. And information about the articulate script should not be placed i

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread Dan Eble
> On Oct 26, 2014, at 16:21 , Joram wrote: > >> The way I have been looking at it, c represents quadruple meter and ¢ >> represents duple. > > This is an interpretation I guessed from 4/4=c and 2/2=¢, too. But I don’t > think it is correct from the above mail by Simon, which I found quite >

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread benko . pal
On 2014/10/26 17:24:01, Dan Eble wrote: On 2014/10/26 07:40:58, benko.pal wrote: > I think we don't want 4/8 displayed as C by default Then this change should not bother you because this new style is not the default. ah, indeed, sorry for the noise. https://codereview.appspot.com/16483004

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread Joram
Hi Dan, Am 26.10.2014 um 19:30 schrieb Dan Eble: On Oct 26, 2014, at 13:36 , Joram wrote: So C instead of 4/4 because of the quarter notes (and not the 4 of them) and ¢ instead of 2/2 for the halves (not the 2 of them). A 4/2 would then be ¢ not C, right? I might be persuaded that you are

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread Dan Eble
On Oct 26, 2014, at 13:36 , Joram wrote: > So C instead of 4/4 because of the quarter notes (and not the 4 of them) and > ¢ instead of 2/2 for the halves (not the 2 of them). A 4/2 would then be ¢ > not C, right? I might be persuaded that you are right by an example of c being used with a meas

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread David Kastrup
Werner LEMBERG writes: Does anyone else see a lot of “Parsed object should be dead” programming errors in the regression test logs? >>> >>> They occur sometimes. If they are a regular, they might point to a >>> problem. >> >> OK, thanks. The reason I noticed them is that they were not

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread Werner LEMBERG
>>> Does anyone else see a lot of “Parsed object should be dead” >>> programming errors in the regression test logs? >> >> They occur sometimes. If they are a regular, they might point to a >> problem. > > OK, thanks. The reason I noticed them is that they were not regular. > > For the record, I

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread Dan Eble
On Oct 26, 2014, at 08:35 , David Kastrup wrote: > Dan Eble writes: > >> Does anyone else see a lot of “Parsed object should be dead” >> programming errors in the regression test logs? > > They occur sometimes. If they are a regular, they might point to a > problem. OK, thanks. The reason I

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread Joram
Am 26.10.2014 um 04:27 schrieb nine.fierce.ball...@gmail.com: Issue 3286: add single-C time signature style This style is identical to single-digit except that C is printed instead of 4 and cut-C is printed instead of 2. I am not sure whether I am mistaken here, but the single-digit is takin

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread nine . fierce . ballads
On 2014/10/26 07:40:58, benko.pal wrote: I think we don't want 4/8 displayed as C by default Then this change should not bother you because this new style is not the default. (I also feel uncomfortable to enter \time 2/1 for the Bach Kyrie or Gratias.) I'm sorry about that. Moving from emo

Re: GUB and mpfr/mpc

2014-10-26 Thread Jan Nieuwenhuizen
David Kastrup writes: >> OK - I've downloaded 14.04, installed it in a VM, updated it, >> installed git, cloned GUB and run make bootstrap. I get: >> >> building package: tools::librestrict >> *** Stage: download (librestrict, tools) >> *** Stage: untar (librestrict, tools) >> *** Stage: patch (l

Re: GUB and mpfr/mpc

2014-10-26 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: "Phil Holmes" > To: "Federico Bruni" > Cc: > Sent: Saturday, October 25, 2014 3:39 PM > Subject: Re: GUB and mpfr/mpc > > >> It's my computer (or strictly, a VM on my computer). >> >> So it would appear that in order to use a curren

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread David Kastrup
Dan Eble writes: > Does anyone else see a lot of “Parsed object should be dead” > programming errors in the regression test logs? They occur sometimes. If they are a regular, they might point to a problem. -- David Kastrup ___ lilypond-devel mailin

Re: GUB and mpfr/mpc

2014-10-26 Thread Phil Holmes
- Original Message - From: "Phil Holmes" To: "Federico Bruni" Cc: Sent: Saturday, October 25, 2014 3:39 PM Subject: Re: GUB and mpfr/mpc It's my computer (or strictly, a VM on my computer). So it would appear that in order to use a current version of gcc, I need at least 12.04 and

Re: Time signature markups

2014-10-26 Thread Trevor Daniels
Dan Eble wrote Sunday, October 26, 2014 12:34 AM > time-signature.cc has a comment at the top > saying, “This file should go; the formatting can completely be done with > markups.” Can anyone point me to a good example of that, or is it a unique > idea? Well, tha

Re: Non-numeric time signatures

2014-10-26 Thread Joram
Am 26.10.2014 um 01:43 schrieb Dan Eble: On Oct 25, 2014, at 17:59 , Simon Albrecht wrote: I think the double c and double cut c symbols are very much non-standard, unlike single cut c for 4/2, which I consider to be in use very widely. With this difference in frequency of use I don’t find

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread James Lowe
On 26/10/14 02:49, Dan Eble wrote: > Does anyone else see a lot of “Parsed object should be dead” programming > errors in the regression test logs? > — > Dan As another example: https://code.google.com/p/lilypond/issues/detail?id=4156 See comment #5 onwards. I think you're hitting the kind of

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ball...@gmail.com)

2014-10-26 Thread benko . pal
I think we don't want 4/8 displayed as C by default, neither 2/4 as cut C. (I also feel uncomfortable to enter \time 2/1 for the Bach Kyrie or Gratias.) https://codereview.appspot.com/164830043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org ht