Re: MY error, but wish the log was clearer.

2009-09-30 Thread Mats Bengtsson
Often, you don't have to explicitly write out any \score{...} block in 
your file, see

http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Introduction-to-the-LilyPond-file-structure#Introduction-to-the-LilyPond-file-structure

However, your feature request is certainly relevant, so I forward it to 
the bug mailing list.


  /Mats

aliteralmind wrote:

I'm using LilyPond for the first time in months. Feels god.

I was about to ask why-the-heck is my LY code being analyzed (I get an
appropriate message when I purposefully put in a syntax error), but when I
fix the error, no PDF is generated. It just stops. I realized, after
halfway-composing my help-me forum message, that I didn't put in the "score"
element.

The log was giving me this:

---
# -*-compilation-*-
Processing `E:/temp/mysong/mysong.ly'
Parsing...
---

Then in just stopped. Nothing. I thought I somehow messed up my computer in
the past months. I put in the "score" element and now it works.

What I WISH the log would say, when no PDF or MIDI is generated, is
something like this:

---
# -*-compilation-*-
Processing `E:/temp/mysong/mysong.ly'
Parsing...
[END. No PDF or MIDI generation requested] 
---


Anyway, I just wanted to make that comment. Thanks for considering.
  




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Order of digits in figured bass

2009-09-30 Thread grisu_76

try this one:

<6 5 3-> <6 3+> <7 3+>

should work; when I remeber to my musical education the order of the figured
bass is

6 - 5 - 3 istead of   3 - 6 - 5

maybe you mean that without the extenders on the 6 : <6 5 3-> <6\! 3+>  <7
3+>, because it makes a difference wheather you let the chord <6 5 3->
followed by a <6\! 3+> ; the 6th on the base of G is another than that on an
A, so the extender might not be correct;

So long!

Christian



Franz-Rudolf Kuhnen wrote:
> 
>> I'm not top posting.
> 
> There is a problem to determine the correct order of the digits in the
> figured 
> bass.
> I want the #3 under the 7.
> 
> %%   Begin example%
> 
> \markup { \large "Bug in the horizontal order of the digits" }
> \markup { \tiny "The #3 should be under the 7"  }
> 
> 
> \version "2.12.0"
> 
> \relative c <<
>  \new Staff {
>   \time 2/4
>   \clef bass
>   d8 g, a4 |
>   d,2 | \bar "|."
>  }
> 
>  \new FiguredBass \figuremode {
>   \override FiguredBass.BassFigure #'font-size = # -3 
>   \set useBassFigureExtenders = ##t
>   s8 <3- 6 5> <6 3+> <7 3+> |
>   s2 |
>  }
>>>
> 
> %%   End example%
> 
> Regards
> Franz-Rudolf Kuhnen
> 
> 
> 
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Order-of-digits-in-figured-bass-tp25670330p25681679.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


VerticalAxisGroup #'remove-first = ##t does not work with \partial r

2009-09-30 Thread Xavier Scheuer
> I'm not top posting.

%% Docs: A staff is considered empty when it contains only multi-measure
%% rests, skips, spacer rests, or a combination of these elements."
%%
%% But because a \partial rest is not one of these elements it prevents
%% \override VerticalAxisGroup #'remove-first = ##t to work if the first
%% empty staff begin, for example, with \partial 16 r16
%% Is it possible to take care of partials when determining empty lines?


\version "2.13.4"
\paper{ ragged-right=##t }

\score {
  <<
\new Staff {
  \partial 16 r16 |  % doesn't work
 % works if we use \partial 16 s16
  R1*4 | \break
  R1*4 | \break
  c''1
  \bar "|."
}
\new Staff {
  \partial 16 c'16 |
  \repeat unfold 4 { c'1 } | \break
  \repeat unfold 4 { c'1 } | \break
  c'1
  \bar "|."
}
  >>

  \layout {
\context {
  \RemoveEmptyStaffContext
  \override VerticalAxisGroup #'remove-first = ##t
}
  }

}


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond