Dan Eble | 26 Oct 03:49 2014
Picon

"Parsed object should be dead" with LilyDev 3

Does anyone else see a lot of “Parsed object should be dead” programming errors in the regression test logs?
— 
Dan

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Dan Eble | 26 Oct 02:34 2014
Picon

Time signature markups

time-signature.cc <http://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?

Thanks,
— 
Dan

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Dan Eble | 25 Oct 20:15 2014
Picon

Non-numeric time signatures

Simon (and all),

Regarding the request to display 4/2 as cut-c by default, https://code.google.com/p/lilypond/issues/detail?id=3286

I think it would make sense to extend the default style to offer a simple way to get the doubled symbols:
    2/1 -> double cut-c (Schubert op. 90 no. 3)
    4/2 -> double c (my obscure hymnal)

You mentioned that you would be satisfied if there were a different style for your alla breve case.  Do you
really need a style or is the following good enough?

timeAllaBreve = {
  \once \override Staff.TimeSignature.stencil = 
  #(lambda (grob)
     (grob-interpret-markup grob
      #{ \markup \musicglyph #"timesig.C22" #}))
  \time 2/1
}

Another thing that occurs to me is a possible parallel with non-numeric tempo.  When the single cut-c symbol
is used to indicate 2/1, does it need to be annotated with text?  If so, would something like \time “alla
breve” 2/1 be any better than the way it has to be done now?

Another potential use for that is \time “swing” 4/4.

Regards,
— 
Dan

_______________________________________________
(Continue reading)

Dan Eble | 25 Oct 17:41 2014
Picon

Bar Line Layering

I am proposing an approach to the issue "Manual barlines overwrite repeat barlines,”
https://code.google.com/p/lilypond/issues/detail?id=3688 .

I think this issue could be addressed by introducing the concept of bar line layers.  The bar lines created
automatically at measure boundaries would be in one layer.  The bar lines created automatically by repeat
structures would be in a layer on top of them.

  top      bar lines created specially by user (is it useful?)
  repeat   bar lines created automatically by repeat structures
  main     bar lines created with \bar x
  timing   bar lines created automatically at measure boundaries
  bottom   bar lines created specially by the user (use described later)

I’m not sure that the “timing" layer should be separate from the “main” layer, but let’s start
with this.

The definition of the set of glyphs to use for a bar line type (normal, end-of-line, beginning-of-line)
would need to indicate when the lower layer should show through.  Whether this would need to be a new option
(e.g. #f) or just a new meaning for “” is discussed later.

The bar engraver would compose the bar types from all layers into a set of glyphs to assign to the BarLine.  For
the example in the issue,

               norm   eol   bol
   repeat     (“.|:”,  #f, “.|:”)
   main       (“||”, “||”, “||”)
   timing     (“|”,   “|”, “|”)
   -------------------------
   result     (“.|:”, “||”, “.|:”)

(Continue reading)

david.nalesnik | 25 Oct 01:18 2014
Picon

Use number-pair-list? with 'control-points (issue 159450043 by david.nalesnik <at> gmail.com)

Reviewers: ,

Message:
Please review.

Description:
Use number-pair-list? with 'control-points

The predicate number-pair-list? is a better fit than list?.

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

Affected files (+1, -1 lines):
   M scm/define-grob-properties.scm

Index: scm/define-grob-properties.scm
diff --git a/scm/define-grob-properties.scm b/scm/define-grob-properties.scm
index  
d6deaec30faa9eee517df088e4c18f72704b9112..54798874db64e1365da38a8ea996c671bd807b70  
100644
--- a/scm/define-grob-properties.scm
+++ b/scm/define-grob-properties.scm
 <at>  <at>  -199,7 +199,7  <at>  <at>  measure of the closeness of the inner stems.  It is  
used for damping
  the slope of the beam.")
       (connect-to-neighbor ,pair? "Pair of booleans, indicating whether
  this grob looks as a continued break.")
-     (control-points ,list? "List of offsets (number pairs) that form
+     (control-points ,number-pair-list? "List of offsets (number pairs)  
that form
(Continue reading)

James Lowe | 24 Oct 09:31 2014
Picon

PATCHES: Countdown for October 27th 2014

Hello,

Here is the current patch countdown list. The next countdown will be on
October 27th.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

David Nalesnik: Patch: Improvements to measure counter
http://code.google.com/p/lilypond/issues/detail?id=4171

David Kastrup: Patch: tie-formatting:
s/Stem::note_head_positions/Stem::head_positions/
http://code.google.com/p/lilypond/issues/detail?id=4170

David Nalesnik: Patch: non-existent procedure-with-setter used in
input/regression/scheme-text-spanner.ly
http://code.google.com/p/lilypond/issues/detail?id=4165

James Lowe: Patch: Added recorder diagram
http://code.google.com/p/lilypond/issues/detail?id=4163

David Kastrup: Patch: Implement -dtags-to-keep and -dtags-to-remove
commandline options
http://code.google.com/p/lilypond/issues/detail?id=4160

(Continue reading)

Phil Holmes | 22 Oct 19:23 2014
Picon

GUB and mpfr/mpc

I'm trying to update GCC on GUB and have a new virtual machine with 
updated versions.  I was having problems getting MPFR to build, but it 
looks like I'ev fixed that with the new VM.  However, it looks to me like 
GCC 4.8.2 has a new dependency on MPC that older versions did not: there 
appears no mention of MPC as a package in the current version of GUB.  My 
most recent failure says this:

checking for the correct version of gmp.h... buggy but acceptable
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 
0.8.0+.

So it looks like we need to add a dependency on MPC.  Problem is, I don't 
have a clue how to do this.  I could try some stuff, but can anyone here 
help with how this dependency should be added to GUB?

TIA.
k-ohara5a5a | 22 Oct 07:58 2014
Picon

Doc: Issue 3324: Add explanation of clashing note columns warning (issue 154640043 by tdanielsmusic <at> googlemail.com)

LGTM

Just for your interest, I have been thinking that when the user gives
explicit \voiceOne or \shiftOn to the voices, Lily should set those
voices at the shifts requested, even if two voices have the same shift
<https://codereview.appspot.com/132110043/>
Currently users are required to set 'ignore-note-collision in these
cases, but then that turns off all the other chord-collision code.

https://codereview.appspot.com/154640043/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/154640043/diff/1/Documentation/usage/running.itely#newcode1112
Documentation/usage/running.itely:1112: ( <at> code{\stemDown}, etc) or
implicitly ( <at> code{\voiceOne}, etc.)
People tend to use \stemDown when they want \voiceTwo, so maybe skip
mention of \stemDown.

I wish there were no shorthand for changing just the stem direction
without the other changes required for consistency.

https://codereview.appspot.com/154640043/
James | 21 Oct 12:04 2014
Picon

PATCHES: Countdown for October 24th 2014

Hello,

Here is the current patch countdown list. The next countdown will be on
October 24th.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

David Nalesnik: Patch: non-existent procedure-with-setter used in
input/regression/scheme-text-spanner.ly
http://code.google.com/p/lilypond/issues/detail?id=4165

Trevor Daniels: Doc: Isolated durations are not mentioned in the LM
http://code.google.com/p/lilypond/issues/detail?id=3813

Trevor Daniels: Slur and Tie subproperties for 'details should be documented
http://code.google.com/p/lilypond/issues/detail?id=1154

____________________

COUNTDOWN:

David Nalesnik: Patch: Improvements to measure counter
http://code.google.com/p/lilypond/issues/detail?id=4171

David Kastrup: Patch: tie-formatting:
(Continue reading)

Kieren MacMillan | 21 Oct 04:18 2014
Picon

disappearing post(s)?

Hello,

Over the past two days, I have sent three versions of almost exactly the same post to these lists — the first
two times cc’ed to both, the last time sent only to -user — but none of those posts have appeared on the
list. This despite several other posts I’ve sent in the interim appearing almost immediately.

What can I do to determine what happened to those posts?
Perhaps an over-eager spam filter got them?

Thanks,
Kieren.
pkx166h | 21 Oct 00:41 2014
Picon

Re: Doc: NR section 3.5.x MIDI file creation tidy up (issue 120480043 by pkx166h <at> gmail.com)

Thanks for the input as always.

Still one question remains (see thread below)

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2702
Documentation/notation/input.itely:2702: (#10) for drums.  Each channel
is allocated for each staff, so a score
On 2014/10/03 21:23:30, Trevor Daniels wrote:
> Staves are assigned to channels in sequence, so a score ...

Done.

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2703
Documentation/notation/input.itely:2703: that contains more than fifteen
staves will result in the extra staffs
On 2014/10/03 21:23:31, Trevor Daniels wrote:
> staffs -> staves

Done.

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2705
Documentation/notation/input.itely:2705: problem if the sharing staffs
have conflicting, channel-based, MIDI
On 2014/10/03 21:23:31, Trevor Daniels wrote:
> staves

Done.
(Continue reading)


Gmane