Comment #4 on issue 1996 by pkx1...@gmail.com: Bar check inside a slur
causes fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
--snip--
It has NOTHING to do with slurs, though.
--snip--
That's correct if you use '~' or even the \< \! construct you get the same
problem
Comment #3 on issue 1996 by percival.music...@gmail.com: Bar check inside a
slur causes fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
the problem isn't whitespace, it's the bar check. you want
c4 ( | c4 )
instead of
c4 | ( c4)
I suppose you could add something to t
Comment #2 on issue 1996 by colinpkc...@gmail.com: Bar check inside a slur
causes fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
I see the bit in LM where slurs are introduced, but the requirement that
they be attached to the previous note is not explicit, and the only
Updates:
Status: Invalid
Comment #1 on issue 1996 by percival.music...@gmail.com: Bar check inside a
slur causes fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
invalid syntax, and the error message is entirely appropriate. The slur
beginning should be attached
Status: Accepted
Owner:
Labels: Type-Defect
New issue 1996 by colinpkc...@gmail.com: Bar check inside a slur causes
fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
Putting a bar check inside a slur causes a fatal error. the followiong code:
\version "2.15.16"
\relat
