Updates:
Status: Started
Labels: -fixed_2_14_1
Comment #5 on issue 1682 by colinpkc...@gmail.com: Website version links
need updating
http://code.google.com/p/lilypond/issues/detail?id=1682
-Eluze and Frederico have pointed out additional version link
inconsistencies, so I b
On 11-06-20 12:31 PM, lilyp...@googlecode.com wrote:
Updates:
Status: Verified
Comment #4 on issue 1682 by colinpkc...@gmail.com: Website version
links need updating
http://code.google.com/p/lilypond/issues/detail?id=1682
With some discomfort at verifying my own fix, we haven't heard
any
with lilypond.org/web i am directed to the above mentioned version!
cheers
Eluze
--
View this message in context:
http://old.nabble.com/probably-old-link-to-2.12.3-tp31889923p31889923.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
Hi,
the link to 2.12 Docs redirects to 2.14 docs:
http://lilypond.org/all.html
Please fix it, thanks
Federico
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #5 on issue 1702 by k-ohara5...@oco.net: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
The old behavior of 2.12 regarding the beam slope was *very* accidental.
(Apply \transpose e c and you find that 2.12 produces a steep beam like
2.14.)
The old spac
Updates:
Status: Verified
Comment #4 on issue 1682 by colinpkc...@gmail.com: Website version links
need updating
http://code.google.com/p/lilypond/issues/detail?id=1682
With some discomfort at verifying my own fix, we haven't heard anything
since, so I'll risk opprobrium to get it o
Comment #35 on issue 1562 by colinpkc...@gmail.com: using \sans on Windows
gives 'gs' error (2.13.53) fails to compile
http://code.google.com/p/lilypond/issues/detail?id=1562
Verified 2.14.1, Win2K
___
bug-lilypond mailing list
bug-lilypond@gnu.or
http://www.aie.com.tn/apo6.html
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Updates:
Status: Verified
Comment #4 on issue 1641 by percival.music.ca: noBeam disables beaming of
prior notes
http://code.google.com/p/lilypond/issues/detail?id=1641
looks fine in 2.15.2.
___
bug-lilypond mailing list
bug-lilypond@gnu.or
Comment #8 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Badness also occurs with tuplets:
\paper { ragged-right = ##f }
\relative c'' { r2 \times 2/3 { r2 bes4 ( } \times 2/3 { a4 aes a } \times
2/3 { a
Updates:
Status: Accepted
Labels: -Priority-Critical -Regression Priority-Medium
Comment #4 on issue 1702 by percival.music.ca: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
Since this was an intentional change, it's not Critical.
I'll agree that
On 20 June 2011 00:10, Keith OHara wrote:
>
> The default spacing between staves was reduced for version 2.14, to 9 staff-
> spaces from the center of one staff to the next.
>
> The method to increase it is a little awkward:
> \new PianoStaff \with {
>\override StaffGrouper
> #'staff-sta
Comment #3 on issue 1702 by mts...@gmail.com: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
I think that, in general, any change to lilypond that occasions an
aesthetic regression, even if it is an intentional change, should be
considered a bug and thus not b
13 matches
Mail list logo
