still a cue problem
I'm quite successfully using \quote, and in parts it works fine.
There is still a problem with full scores.
Assume that the file `trumpet.ily' is included both by `trumpet.ly'
(to create the trumpet part) and `score.ly' (to create the full
score). To produce a cue I have this code in trumpet.ily:
<< { R1 } \\
{ \small \quote "flute" 1 } >>
This works fine in trumpet.ly since the both the first and the second
block contains data. In `score.ly', only the upper block is used
because \quote intentionally expands to nothing by saying
\set Score.quotedEventTypes = #'()
at the top of `score.ly'. Consequently, the code is equivalent to
<< { R1 } \\
{} >>
As you can see, the second group is empty. Lilypond accepts that, but
it doesn't completely ignore the empty group: It shifts the whole rest
up. To get correctly positioned whole rests I currently have to do
this:
\tag #'score { R1 }
\tag #'trumpet << { R1 } \\
{ \small \quote "flute" 1 } >>
(and applying the tags accordingly), but this is really ugly IMHO and
a lot of additional work.
Is it possible to make lilypond really ignore an empty group, without
any side effects? Perhaps \quote can expand to an object which says
`Please ignore me completely'. Or am I missing something?
Werner
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Wed, 2004-09-22 at 22:04, Jan Nieuwenhuizen wrote: > David Bobroff writes: > > > CVS ChangeLog 1.2624 on 'make all' exits like this: > > Do you still have this problem? What version of bison do you use? > > > bison -o out/parser.cc parser.yy > > mv -f parser.yy.tab.c out/parser.cc # bison < 1.30 > > mv: can't stat source parser.yy.tab.c > > make[1]: [out/parser.cc] Error 1 (ignored) > > rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep > > ./out/parser.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED > > -Iinclude -I./out -I../flower/include -I../flower/./out > > -I../flower/include -O2 -finline-functions -g -pipe > > -I/usr/include/python2.2 -O2 -finline-functions -g -pipe > > -I/usr/include/python2.2 -W -Wall -Wconversion -o out/parser.o > > out/parser.cc > > parser.yy: In function `int yyparse(void*)': > > parser.yy:696: non-lvalue in assignment > > make[1]: *** [out/parser.o] Error 1 > > rm out/lexer.cc out/parser.cc > > make[1]: Leaving directory `/usr/src/lilypond/lily' > > make: *** [all] Error 2 > > [EMAIL PROTECTED] lilypond]# > > > > -David No, it's fine now. I think with the update that followed this CVS version there was an update to parser.yy that was likely the culprit. Sorry I didn't post an "ok now". -David ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug status
On Tuesday 21 September 2004 00.27, Erik Sandberg wrote: > I checked through the bugs quickly, and I only found one bug that makes 2.3 > strictly worse than 2.2, and hence prevent 3.0. That's titling-piece.ly. Add boxed-rehearsal-mark to this. It is now worse than in 2.2, the bottom line is way off. see attachment. Erik <>___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Thursday 23 September 2004 00.04, Jan Nieuwenhuizen wrote: > David Bobroff writes: > > CVS ChangeLog 1.2624 on 'make all' exits like this: > > Do you still have this problem? What version of bison do you use? Probably not; I had exactly the same error and it has now been fixed (by Werner, it seems) Erik ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
David Bobroff writes: > CVS ChangeLog 1.2624 on 'make all' exits like this: Do you still have this problem? What version of bison do you use? > bison -o out/parser.cc parser.yy > mv -f parser.yy.tab.c out/parser.cc # bison < 1.30 > mv: can't stat source parser.yy.tab.c > make[1]: [out/parser.cc] Error 1 (ignored) > rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep > ./out/parser.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED > -Iinclude -I./out -I../flower/include -I../flower/./out > -I../flower/include -O2 -finline-functions -g -pipe > -I/usr/include/python2.2 -O2 -finline-functions -g -pipe > -I/usr/include/python2.2 -W -Wall -Wconversion -o out/parser.o > out/parser.cc > parser.yy: In function `int yyparse(void*)': > parser.yy:696: non-lvalue in assignment > make[1]: *** [out/parser.o] Error 1 > rm out/lexer.cc out/parser.cc > make[1]: Leaving directory `/usr/src/lilypond/lily' > make: *** [all] Error 2 > [EMAIL PROTECTED] lilypond]# > > -David > > > > ___ > lilypond-devel mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/lilypond-devel > > -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond-book status
On 22-Sep-04, at 1:49 AM, Mats Bengtsson wrote:
Has anyone tried lilypond-book with LaTeX recently?
We have often had bugs there in the major releases.
I've been using lily-book, and there's two major issues IMO:
1) Is raggedbottom supposed to work with lilypond-book? So far I
haven't been able to make it work, but I confess I haven't spent a lot
of time investigating it.
2) Metronome mark padding problems. (perhaps this is just an OSX
issue)
save the two files:
--foo.ly
\score {
\relative c'''{
\tempo 4=80
\repeat unfold 6 {c4 c c c c c c c c c c c c c c c \break }
}
\paper {
\context { \Score \override MetronomeMark #'padding = #16.0 }
\context{ \Staff minimumVerticalExtent = #'(-6 . 6) }
}
}
--
bar.lytex
\documentclass[letterpaper]{article}
\begin{document}
\lilypondfile{foo.ly}
\end{document}
-
lilypond foo.ly
%% produces expected output. Huge space between MetronomeMark and the
first line of staff
lilypond-book bar.lytex; latex bar.tex (etc...)
%% there's a huge space between the first line of the staff and the
second line. No extra space between first line of staff and
MetronomeMark, but the stem of MetronomeMark is raised.
I've got an example of this (produced from an earlier file) at
http://www.sfu.ca/~gperciva/foo.pdf
(it has some extra text at the beginning of the lytex, but that's
nothing major)
Apart from that, lilypond-book looks great!
- Graham
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
release-critical bugs
Hi, Due to lack of time I will not add release-critical bugs to the database; I assume their priority are high enough so they will be fixed soon anyways. The bug list is a long-term thing anyways. My complete buglist locally is partially consisting of a local mailbox. So, don't trust that lilypond can be released once the bug repository looks fine! I will yell if you release a release candidate which still has a release-critical bug. Erik ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Docs for 3.0
On Monday, 2004-09-20 at 22:31 -0700, Graham Percival wrote: > The real problem is "piano-dynamics.ly" (dynamics centered between the > two piano staffs). It sounds like a good template to have, but I don't > understand the template myself, and there's a bunch of ugly stuff in > there (like extra-offset). Could a piano player have a look at this > and simplify it? Or make a completely new template that does the same > thing? This template has been really useful for me when engraving children's piano pieces. I just had to adjust the extra-offset a tiny bit to the right so the dynamics don't sometimes overlap with bar lines. It would be nice if there was a simpler way to achieve centered dynamics, but so far I don't know LilyPond well enough to know where to start. But I have plenty of .ly files using centered dynamics to test new ideas on. ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug status
Has anyone tried lilypond-book with LaTeX recently? We have often had bugs there in the major releases. /Mats Erik Sandberg wrote: I checked through the bugs quickly, and I only found one bug that makes 2.3 strictly worse than 2.2, and hence prevent 3.0. That's titling-piece.ly. Erik ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
\tag with multiple tags
I would like to have a list in \keepWithTag (and the still undocumented \removeWithTag): \keepWithTag #'(foo bar) \music This is, both tags `foo' and `bar' are retained. Werner ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
