bison-3.0 fix lilypond

[Thomas Klausner]

Hi!

The latest stable and development branches of lilypond do not compile with
the recently released bison-3.0.

The following patch fixes this (sorry, whitespace may be off):

--- lily/parser.yy.orig 2013-01-04 13:41:57.0 +
+++ lily/parser.yy
@@ -100,7 +100,7 @@ or
 
 
 
-%pure_parser
+%pure-parser
 %locations
 
 

While I'm here, I'll just report a minor issue too:
scripts/auxiliar/cg-section.sh uses the unportable == operator for
test(1), only supported by bash, not even by GNU coreutils. Please use the
portable = instead.

--- scripts/auxiliar/cg-section.sh.orig 2013-01-04 13:41:56.0 +
+++ scripts/auxiliar/cg-section.sh
@@ -31,7 +31,7 @@ EOF
 exit $1
 }
 
-if [ $1 == '-h' ] || [ $1 == '--help' ]; then
+if [ $1 = '-h' ] || [ $1 = '--help' ]; then
 usage 0
 fi
 

Thanks,
 Thomas
(please cc me, not subscribed)


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

Re: bison-3.0 fix lilypond

[David Kastrup]

Thomas Klausner t...@giga.or.at writes:

 Hi!

 The latest stable and development branches of lilypond do not compile with
 the recently released bison-3.0.

 The following patch fixes this (sorry, whitespace may be off):

 --- lily/parser.yy.orig 2013-01-04 13:41:57.0 +
 +++ lily/parser.yy
 @@ -100,7 +100,7 @@ or
  
  
  
 -%pure_parser
 +%pure-parser
  %locations

That does not seem like a bison-3.0 fix: according to the documentation,
%pure-parser is the right form even for 2.6.2.  The question is what
effect the wrong declaration had, if any.

 While I'm here, I'll just report a minor issue too:
 scripts/auxiliar/cg-section.sh uses the unportable == operator for
 test(1), only supported by bash, not even by GNU coreutils. Please use the
 portable = instead.

Typical bashism, yes.  Personally, I prefer using case/esac for almost
everything.  That usually is quite more flexible and has been a shell
builtin for quite longer than test.

-- 
David Kastrup


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

buggy quoting as of first note

[Jean-Charles Malahieude]

Hi all!

When using *quoteDuring*, I would expect the third staff not to 
displayed at normal size, not as a *cueVoice*.


\version 2.17.22

music = { e'1 c' }

\addQuote quoted { \music }

quoteA = { R1 \quoteDuring quoted { s1 } }

quoteB = { \quoteDuring quoted { s1 } R1 }

\score {
   \new Staff { \music }
 \new Staff { \quoteA }
 \new Staff { \quoteB }
  
  \layout { }
}

Cheers,
Jean-Charles
attachment: quote.preview.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: buggy quoting as of first note

[Keith OHara]

Jean-Charles Malahieude lilyfan at orange.fr writes:

 When using *quoteDuring*, I would expect the third staff not to 
 displayed at normal size, not as a *cueVoice*.

I could not find this in the bug list, so added 
http://code.google.com/p/lilypond/issues/detail?id=3489

You can avoid the problem by creating the Voice explicitly.

   \new Staff { \quoteB }
\new Staff \new Voice { \quoteB }


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