Status: Accepted
Owner:
Labels: Type-Scripts Priority-Low Frog
New issue 1749 by lemniska...@gmail.com: articulate script doesn't support
partial ties
http://code.google.com/p/lilypond/issues/detail?id=1749
\articulate cannot properly process partially tied chords (i.e. when a
tilde is
I'm not a good schemer, so i cannot fix it, but i've added it to the tracker:
http://code.google.com/p/lilypond/issues/detail?id=1745
Please remember to forward such things to bug-lilypond -
i found this on -user only by accident :)
cheers,
Janek
2011/6/6 Peter Chubb :
> I've taken a look at th
Le 7 juil. 2011 à 12:13, lilyp...@googlecode.com a écrit :
>
> Comment #3 on issue 1747 by brownian.box: parallelmusic problem: q-notation
> does not work in \relative
> http://code.google.com/p/lilypond/issues/detail?id=1747
>
> Probably, this is the issue of chord repetition in relative mode:
Updates:
Labels: -Patch-review
Comment #3 on issue 1664 by pkx1...@gmail.com: Add link to LSR on web site
http://code.google.com/p/lilypond/issues/detail?id=1664
Pushed as 4d828c178c06d87332301030cc02dde9a9403538
___
bug-lilypond mailing list
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_5 backport
Comment #3 on issue 1733 by n.putt...@gmail.com: \displayLilyMusic ignores
\tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
d5766025a1573c709dfa3c9663c1c6b903abec24
_
Comment #4 on issue 1747 by n.putt...@gmail.com: parallelmusic problem:
q-notation does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Probably, this is the issue of chord repetition in relative mode:
I think this snippet is correct. This commit changed the
Updates:
Status: Fixed
Owner: mts...@gmail.com
Labels: fixed_2_15_5
Comment #2 on issue 1748 by n.putt...@gmail.com: Defect in glissando
handling
http://code.google.com/p/lilypond/issues/detail?id=1748
Presumably with commit 0c258f3f339573d25080dadd0a1a5078ec35b09a
> I'm not top-posting
Thanks to both for your interesting follow-ups. Your information, Neil, makes
perfect sense.
Only I feel this information is perhaps lacking from the docs. I would have
expected the full story to be in
http://lilypond.org/doc/v2.14/Documentation/notation/displaying-pitches#a
Comment #11 on issue 153 by reinhold...@gmail.com: \once \set fails to
restore previous setting
http://code.google.com/p/lilypond/issues/detail?id=153
See
Property_iterator::once_finalization (SCM ctx, SCM music)
Property_iterator::do_quit ()
in lily/property-iterator.cc. \once\set inst
On 7 July 2011 06:54, Dmytro O. Redchuk wrote:
> NR says:
>
> % -8<--
> This function is called as follows:
>
> \new Staff <<
> #(set-accidental-style 'voice)
> { … }
> >>
>
> The accidental style applies to the current Staff by default [...]
>
Comment #1 on issue 1748 by x.sche...@gmail.com: Defect in glissando
handling
http://code.google.com/p/lilypond/issues/detail?id=1748
Mike stated it is fixed in master.
https://lists.gnu.org/archive/html/lilypond-devel/2011-07/msg00321.html
Presumably with commit
0c258f3f339573d25080dadd0a1a5
On 7 July 2011 15:13, Dmytro O. Redchuk wrote:
>
> Hi, Xavier!
>
> Sorry for so late reply, I've been flagged your message on Wed 06 Apr 2011,
> actually .)
>
> Anyway: this is issue 1286:
> http://code.google.com/p/lilypond/issues/detail?id=1286
>
> Page breaking works fine when I replace all you
Comment #10 on issue 153 by d...@gnu.org: \once \set fails to restore
previous setting
http://code.google.com/p/lilypond/issues/detail?id=153
You have not answered my last question. When is the meaning of \once\set
supposed to be reverted? I can't be when the time advances, since \set is
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1748 by philehol...@googlemail.com: Defect in glissando handling
http://code.google.com/p/lilypond/issues/detail?id=1748
Regtests show regression between 2.15.3 and 15.4. See attached image.
Attachments:
On Sun 24 Apr 2011, 18:51 Valentin Villenave wrote:
> On Wed, Apr 20, 2011 at 4:47 PM, m...@apollinemike.com
> wrote:
> > That said, the following code still produces the same message:
Hi, Valentin!
Yes, indeed, sorry for so late reply .)
> Greetings everybody, hi Mike,
>
> Since there's a lot
On Wed 06 Apr 2011, 16:17 Xavier Scheuer wrote:
> It seems single-line (single-system) scores prevent _totally_ page
> breaks and thus produce overflow and bad output.
Hi, Xavier!
Sorry for so late reply, I've been flagged your message on Wed 06 Apr 2011,
actually .)
Anyway: this is issue 1286:
h
On Mon 14 Feb 2011, 08:43 Janek Warchoł wrote:
> hi,
Hi, Janek,)
> The amount of whitespace after the barline is fixed, while it should depend
> on whether the first note in the measure has an accidental or not. This
> results in notes being too far from the barline, especially when there is
> onl
Comment #9 on issue 153 by lemzw...@googlemail.com: \once \set fails to
restore previous setting
http://code.google.com/p/lilypond/issues/detail?id=153
Well, I don't mind the syntax – IIRC, it's you who've asked for unifying
\set and \override into a single command (and I second that sugges
Comment #2 on issue 1747 by brownian.box: parallelmusic problem: q-notation
does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Yes, I see now... So is this one a duplicate for Issue 1110?
___
bug-lilypond mailing li
Comment #15 on issue 1701 by brownian.box: default accidental style prints
too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
Sorry, did not test with 2.14.2 yet (Carl, should "fixed_2_14_2" be added?
Or "backported" or the like?).
_
Comment #3 on issue 1747 by brownian.box: parallelmusic problem: q-notation
does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Probably, this is the issue of chord repetition in relative mode:
\version "2.15.4"
% should be identical:
\new Voice {
\relative
Updates:
Status: Fixed
Comment #14 on issue 1701 by brownian.box: default accidental style prints
too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
Sorry, did not test with 2.14.2 yet (Calr, should "fixed_2_14_2" be added?
Or "backported" or the like?
Comment #1 on issue 1747 by x.sche...@gmail.com: parallelmusic problem:
q-notation does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
There is also an issue with "q-notation" and wrong octave identified in
#1110 .
_
Updates:
Status: Verified
Comment #13 on issue 1615 by brownian.box: lily-git.tcl not working:
savannah sometimes does not like git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
(No comment was entered for this change.)
___
On Wed 06 Jul 2011, 15:05 Arno Waschk wrote:
> dear list,
>
> the following
>
> \version "2.15.4"
> \parallelMusic #'(abc def) {
> 2 q|
> 2 q|
> % 2 2 |
> % 2 2 |
> }
>
> \new Staff {<<
> \relative c'' \abc
> \relative c' \def
> >>}
>
>
> does not produce the desired result
Updates:
Status: Verified
Comment #13 on issue 1701 by brownian.box: default accidental style prints
too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
Initial snippet looks like in comment #3.
___
bug-lilypo
On Tue 05 Jul 2011, 13:01 Jan Nieuwenhuizen wrote:
>
> ...and thus breaks documentation links, notably info pages.
> This will probably happen in all binary builds, it happens
> in GUB.
>
> 12:54:19 janneke@abc:/var/www/lilypond/download/binaries/documentation
> $ tar taf lilypond-2.13.47
Comment #1 on issue 1699 by mts...@gmail.com: Automated numbering for
footnotes
http://code.google.com/p/lilypond/issues/detail?id=1699
Passes regtests.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1747 by brownian.box: parallelmusic problem: q-notation does not
work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Reported by Arno Waschk,
http://lists.gnu.org/archive/html/bug-lilypond/2011-07
Status: Accepted
Owner:
Labels: Type-Build Priority-Medium
New issue 1746 by brownian.box: v2.13.48 docball adds offline-root/
directory
http://code.google.com/p/lilypond/issues/detail?id=1746
Reported by Jan Nieuwenhuizen,
http://lists.gnu.org/archive/html/bug-lilypond/2011-07/msg00120.
On Thu 07 Jul 2011, 10:33 I wrote:
> On Tue 05 Jul 2011, 23:22 David Nalesnik wrote:
> > I've also attached a pared-down version of the file which should work
> > in either release, as is. It distills the problem a little more -- at
> > the expense of centering the number directly on the beam . .
Comment #1 on issue 1745 by brownian.box: Strange vertical space above
TupletBracket when moving it for the sake of cross-staff beamed tuplets
http://code.google.com/p/lilypond/issues/detail?id=1745
For the record -- tuplet number placement is a subject of issue 696.
___
On Tue 05 Jul 2011, 23:22 David Nalesnik wrote:
> Hi, Colin --
>
> On 7/5/11, Colin Campbell wrote:
> >
> > This will probably require an issue, David, but could you send the code
> > you used to produce the 2.12.3 version, please? I can't reproduce the
> > previous stable example, in order to c
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1745 by brownian.box: Strange vertical space above TupletBracket
when moving it for the sake of cross-staff beamed tuplets
http://code.google.com/p/lilypond/issues/detail?id=1745
Reported by David Nalesnik, see here:
h
34 matches
Mail list logo
