snippet throws programming errors

2015-01-13 Thread Villum Sejersen
Well, on my system your snippet as you have written it throws no error 
whatsoever... The result is exactly as I believe is the one you expected.


I rather suspect your way of organizing the lilypond file is creating 
the error, or - perhaps more understandable - the fact that you are on a 
mac may be the reason?


My own system is a linux debian testing, vigorously updated.

--
yours,
Villum Sejersen
Nørregade  1 A
DK-4500  Nykøbing Sjælland
mobil   +45   30 34  03 44


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: snippet throws programming errors

2015-01-13 Thread Jacques Menu
Grouping the key with the music is fine and gives no error (I’m using a Mac). 
That’s reasonable since the key may change at places within the music.

JM

%%%
\version 2.19.15

music = \relative c'' {
  \key c \major
  e2 g,
  \key e \minor
  e2 g,
}

\score  {

  \new Staff 
\music
  

  \layout {
\context { \Voice \consists Ambitus_engraver }
  }

}
%%%

 Le 13 janv. 2015 à 12:30, Villum Sejersen v...@privat.tdcadsl.dk a écrit :
 
 Well, on my system your snippet as you have written it throws no error 
 whatsoever... The result is exactly as I believe is the one you expected.
 
 I rather suspect your way of organizing the lilypond file is creating the 
 error, or - perhaps more understandable - the fact that you are on a mac may 
 be the reason?
 
 My own system is a linux debian testing, vigorously updated.
 
 -- 
 yours,
 Villum Sejersen
 Nørregade  1 A
 DK-4500  Nykøbing Sjælland
 mobil   +45   30 34  03 44
 
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


snippet throws programming errors

2015-01-12 Thread Cynthia Karl
The following snippet:

\version 2.19.15

music = \relative c'' { e2 g, }
 
\score  {
  \new Staff  \key c \major  \music 
  \layout {
\context { \Voice \consists Ambitus_engraver } 
  }
}

throws the following two programming errors:

*   programming error: Note-column without heads and stem
continuing, cross fingers
*   programming error: note-column has no direction
continuing, cross fingers

The pdf output looks perfect, so I guess the finger crossing worked.  

These two errors can be eliminated in any one of several ways:

* eliminate \key c \major from the \new Staff statement (!!!)
* replace ... with {...} on the \new Staff statement.
* eliminate the \context statement in the \layout block

Where can I find out what's happening here?  and is there a way to suppress 
these errors similar to the way that warnings can be suppressed.  
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: snippet throws programming errors

2015-01-12 Thread Jim Long
On Mon, Jan 12, 2015 at 05:25:55PM -0600, Cynthia Karl wrote:
 The following snippet:
 
 \version 2.19.15
 
 music = \relative c'' { e2 g, }
  
 \score{
   \new Staff  \key c \major  \music 
   \layout {
 \context { \Voice \consists Ambitus_engraver } 
   }
 }

Your Staff line is equivalent to:

\new Staff
  
{ \key c \major }
{ \music }
  

Thus, there is no music in the first expression.  In a nutshell, that
is what is causing your issue.

...
   * replace ... with {...} on the \new Staff statement.
...

That is the correct solution, IMO.


HTH,

Jim


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: snippet throws programming errors

2015-01-12 Thread Keith OHara
Cynthia Karl pckarl at mac.com writes:

 \score{
   \new Staff  \key c \major  \music 
   \layout {
 \context { \Voice \consists Ambitus_engraver } 
   }
 }
 
 throws the following two programming errors:

Programming errors are intended to report conditions that a programmer
thinks cannot happen in correct operation of the program. But with a large 
program with large numbers of people working on it, what one programmer thinks 
is an obviously-wrong situation might be considered a harmless null-case by 
another programmer.

In this case, \key c\major is alone in its own voice with no notes, so the 
Ambitus_engraver for that voice creates an ambitus with no note-heads,
but the note-column engraver thinks that an ambitus with nothing in it
must be an error.

 Where can I find out what's happening here?
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=lily/note-column.cc

  and is there a way to suppress these errors similar to the way that
 warnings can be suppressed.  

I don't think so. 
I would write
 \new Staff \new Voice  \key c \major  \music 

so that LilyPond's right hand doesn't fret about the empty voice for which 
her left hand created an empty ambitus


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: snippet throws programming errors (Jim Long) 53

2015-01-12 Thread Keith OHara
Cynthia Karl pckarl at mac.com writes:

 IMO, the problem is that my simple snippet causes LilyPond to declare that
 programing errors have occurred.  Programming errors are a serious 
 problem.  Programming errors are only
 solved by correcting the program, not by avoiding them by modifying the 
 input to the program.

This is, of course, the cue for the rest of us to say :
You've been using LilyPond longer than me; why haven't you yet corrected
 this serious problem !? 

  You are
 suggesting that LilyPond is incapable of diagnosing a simple syntax 
 error in its input.
 

LilyPond is very accepting of varied syntax, makes up the missing parts,
and in this case creates situations that other of its various spare-time
programmers thought could only indicate an error.





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user