> > > Could you tell me what the exact meanings of these barlines are?
> > > The NR hasn't a literal description:
> >
> > Indeed. So here it is.
>
> These are shown in 1.2.5 Bar lines -- but of course they're only
> shown in the picture example. Again, all of the documentation is
> written with t
Hi David, hi everybody.
David's feature request has been officially added as
http://code.google.com/p/lilypond/issues/detail?id=559
I'm both happy and sad to admit this request: I am happy to see that
people like David care about making LilyPond an even better program,
through such documented req
Issue 559: Feature request: support accordion with standard bass
http://code.google.com/p/lilypond/issues/detail?id=559
New issue report by v.villenave:
% This (very complete and documented) feature request was made
% by David Kastrup on the bug-list on Jan. 13th 2008, after
% a short discussion
2008/1/14, Andrew Hawryluk <[EMAIL PROTECTED]>:
> I think this is a bug. I expect my code to produce two crescendo
> marks, but the second one doesn't appear.
This doesn't happen when you have a note or a normal rest after the
line break, so it must have something to do with the use of a
MultiMeas
Issue 558: Spanner 'Hairpin' error when a MultiMeasureRest occurs after
a line break
http://code.google.com/p/lilypond/issues/detail?id=558
New issue report by v.villenave:
% when compiling the following example, a 'programming error'
% is displayed and the second crescendo is not printed.
% th
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #8 by v.villenave:
Oh, I'm sorry. I was afraid it could be inappropriate, but it was just
too tempting
to see Joe's patches! (Besides, I typed 2_11_28 instead of 2_11_28.)
OK, back
I think this is a bug. I expect my code to produce two crescendo
marks, but the second one doesn't appear.
\version "2.11.36"
\paper {ragged-right = ##t}
\relative c'' { c1\< R1\! c1\< \break R1\! }
invoking LilyPond produces a programming error:
cresctobreak.ly:6:20: warning: programming error:
On 13 Jan 2008, at 22:50, Graham Percival wrote:
I know
that learning scheme may seem daunting, but realistically
speaking, it's the only way this will get implemented.
One Scheme learning book is Abelson, Sussman, "Structure and
Interpretation of Computer Programs".
Hans Åberg
___
On Sun, 13 Jan 2008 21:33:20 + (UTC)
Carl Sorensen <[EMAIL PROTECTED]> wrote:
> David Kastrup gnu.org> writes:
>
> > Accordion with standard bass is not well-supported in Lilypond.
>
> This is a nice description of accordion notation. Such a discussion
> would normally take place on user,
David Kastrup gnu.org> writes:
>
>
> Accordion with standard bass is not well-supported in Lilypond.
David,
This is a nice description of accordion notation. Such a discussion would
normally take place on user, not on bugs. Since I'm working on the Gmane
interface, I can't easily forward it
On Sun, 13 Jan 2008 09:57:52 +0100 (CET)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > Could you tell me what the exact meanings of these barlines are?
> > The NR hasn't a literal description:
>
> Indeed. So here it is.
These are shown in 1.2.5 Bar lines -- but of course they're only
shown in t
Issue 467: Two calls to set-octavation confound intervening clef change
http://code.google.com/p/lilypond/issues/detail?id=467
Comment #7 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -fixed_2_11_38
--
You received this message because you are l
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #7 by gpermus:
This isn't fixed; Joe was asking Han-Wen to examine the patches to see
if they were
acceptable.
Valentin: in general, don't change the status to "fixed" or
add "fix
Issue 467: Two calls to set-octavation confound intervening clef change
http://code.google.com/p/lilypond/issues/detail?id=467
Comment #6 by v.villenave:
Thanks a LOT! This was really an annoying bug (speaking from personal
experience).
I'll verify it as soon as I can.
Issue attribute updates
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #6 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Labels: fixed_2_11_28
--
You received this message because you are listed in the owner
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #5 by v.villenave:
Thank you very much Joe.
Maybe I was the one supposed to apply your patches (hope I did nothing
wrong though).
If I was not, or if I did wrong, please apologize.
Issue 467: Two calls to set-octavation confound intervening clef change
http://code.google.com/p/lilypond/issues/detail?id=467
Comment #5 by joeneeman:
See the attachments to 533 for patches fixing this bug (parts 1, 6 and
7 of the
patch set, I think).
Issue attribute updates:
Status:
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #4 by joeneeman:
Here is a set of patches; number 5 fixes this bug and it should apply separately
from the others. I´ve attached others here too because I don´t know
when I will next
Issue 528: wish: underline markup
http://code.google.com/p/lilypond/issues/detail?id=528
Comment #6 by erlenda:
Oops, I've fixed the x-extent :-) The y-extent is not needed, I don't
see any use for it here.
As for your snippet, this works as you expect:
\markup \center-align \underline { foo ba
> :|two repeat dots followed by a thick line
Oops! This should be
:|two repeat dots, a thin line, and a thick line
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
[I've forwarded your mail to the bug-lilypond list.]
> Could you tell me what the exact meanings of these barlines are?
> The NR hasn't a literal description:
Indeed. So here it is.
> \bar ".|" \bar ".|." \bar "|." \bar ":|:"
> (What kind of repetition barline is it?)
| a thin line
||
21 matches
Mail list logo
