On Wed 17 Nov 2010, 16:18 Ralph Palmer wrote:
> Greetings, Anders Vinjar -
>
[...]
> Thank you for your email. This has been added as issue # 1410 :
> http://code.google.com/p/lilypond/issues/detail?id=1410
>
> Pondly,
>
> Ralph
On Tue 14 Dec 2010, 16:02 Phil Holmes wrote:
> Bump. Could a bug
Updates:
Status: Verified
Comment #2 on issue 1383 by Carl.D.Sorensen: Make error when invoking `make
maintainerclean'
http://code.google.com/p/lilypond/issues/detail?id=1383
(No comment was entered for this change.)
___
bug-lilypond maili
Updates:
Status: Verified
Comment #7 on issue 1265 by pnorcks: Avoid compilation and run-time
deprecation warnnings from Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1265
(No comment was entered for this change.)
___
bug-lil
Updates:
Status: Verified
Comment #5 on issue 1249 by pnorcks: Avoid compilation errors using Guile
V2 during initialization - Part 1 ly-syntax-constructors.scm
http://code.google.com/p/lilypond/issues/detail?id=1249
(No comment was entered for this change.)
Updates:
Status: Verified
Comment #8 on issue 1407 by Carl.D.Sorensen: Glyphs with an extra Y-offset
are not positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
Verified. THanks, Patrick
Attachments:
Verify-1407.png 2.0 KB
Comment #7 on issue 1407 by pnorcks: Glyphs with an extra Y-offset are not
positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
Oh man, I wish this tracker warned about new comments being added at the
same time by different users. :)
Graham, it's not a problem. I
Comment #6 on issue 1407 by pnorcks: Glyphs with an extra Y-offset are not
positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
Okay, to verify this issue, first install the "Khmer OS" font. You can
download the font by clicking the "KhmerOS_.ttf" link located on th
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium Frog Maintainability
New issue 1453 by percival.music.ca: lilybuntu-creation instructions
http://code.google.com/p/lilypond/issues/detail?id=1453
It would be great if somebody could dump the instructions from this email
in
Comment #5 on issue 1407 by percival.music.ca: Glyphs with an extra
Y-offset are not positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
If "right now" you mean "in the next 2-6 weeks until 2.14 is released",
then yes. If you'd mentioned it earlier (or later), then
Comment #4 on issue 1386 by Carl.D.Sorensen: Tied harmonics in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=1386
A regression test input/regression/tablature-harmonic-tie.ly has been
pushed.
The regtest is part of .44, but the fix is part of .42
Someone other than me should v
Updates:
Status: Verified
Comment #8 on issue 1363 by Carl.D.Sorensen: Language links in manual pages
should be right from start and kept intact by web_post.py
http://code.google.com/p/lilypond/issues/detail?id=1363
Verified for the reported links.
Thanks,
Carl
Comment #4 on issue 1407 by pnorcks: Glyphs with an extra Y-offset are not
positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
Hmm, I can post a regtest to the tracker, if that works.
I don't want to add one to input/regression because this problem only
appears whe
Comment #3 on issue 1386 by v.villenave: Tied harmonics in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=1386
Sorry, I meant that the patch that addressed this has now been merged in
the master code branch :-)
___
bug-lilypond mailin
Comment #3 on issue 1407 by Carl.D.Sorensen: Glyphs with an extra Y-offset
are not positioned correctly
http://code.google.com/p/lilypond/issues/detail?id=1407
Patrick,
Do you have a regtest for this so we can validate it?
Thanks,
Carl
___
bug
Updates:
Status: Verified
Comment #34 on issue 1336 by Carl.D.Sorensen: skipTypesetting segfaults
when set during a skipBars-induced MultiMeasureRest spanner
http://code.google.com/p/lilypond/issues/detail?id=1336
Verified, and regression tests pushed. Regtests are not part of .43, b
Updates:
Status: Verified
Comment #6 on issue 1440 by Carl.D.Sorensen: \book(part) containing
page-marker as only element segfaults
http://code.google.com/p/lilypond/issues/detail?id=1440
Verified, and a regtest has been pushed (although it didn't make it in the
2.13.43 release).
Updates:
Status: Verified
Comment #5 on issue 810 by Carl.D.Sorensen: Improving tablatures support
(rhythm notation, etc.)
http://code.google.com/p/lilypond/issues/detail?id=810
The file tablature-harmonic-functions.ly demonstrates the double stems for
half notes.
__
Comment #1 on issue 1450 by k-ohara5...@oco.net: Collision between slur and
text in les-nereides regtest
http://code.google.com/p/lilypond/issues/detail?id=1450
It is not obvious from the output, but the colliding slurs cross staves.
These slurs, and also the fingering 2 that is moved by the
Updates:
Status: Verified
Comment #3 on issue 1452 by PhilEHolmes: asldjf
http://code.google.com/p/lilypond/issues/detail?id=1452
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.or
Updates:
Status: Invalid
Comment #2 on issue 1452 by PhilEHolmes: asldjf
http://code.google.com/p/lilypond/issues/detail?id=1452
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org
Comment #1 on issue 1452 by palmer.r.violin: asldjf
http://code.google.com/p/lilypond/issues/detail?id=1452
Hmm. I was trying to start the entry process for a non-existent issue, so
that I could see what the choices for categories are. I did not intend to
actually submit this issue. Whomever
Updates:
Labels: Priority-Medium
Comment #1 on issue 1443 by PhilEHolmes: bookTitleMarkup to fill exactly
one page (with stretching!) and contain page breaks
http://code.google.com/p/lilypond/issues/detail?id=1443
(No comment was entered for this change.)
Attachments:
titlepa
Updates:
Labels: Priority-High
Comment #2 on issue 1442 by PhilEHolmes: staff-staff padding all appears
after the last nonstaff
http://code.google.com/p/lilypond/issues/detail?id=1442
(No comment was entered for this change.)
___
bug-lilyp
Updates:
Labels: Priority-Medium
Comment #1 on issue 1431 by PhilEHolmes: Enhancement - add spiccato
articulation symbol
http://code.google.com/p/lilypond/issues/detail?id=1431
(No comment was entered for this change.)
___
bug-lilypond mai
Updates:
Labels: Priority-Medium
Comment #1 on issue 1380 by PhilEHolmes: Switching staves with \times looks
odd
http://code.google.com/p/lilypond/issues/detail?id=1380
(No comment was entered for this change.)
___
bug-lilypond mailing lis
Updates:
Labels: Priority-Medium
Comment #1 on issue 1410 by PhilEHolmes: Rest in lower voice should be
placed above notes in in upper if voices are crossed.
http://code.google.com/p/lilypond/issues/detail?id=1410
(No comment was entered for this change.)
Attachments:
1410.pn
Comment #2 on issue 1451 by pnorcks: \parenthesize should enclose entire
objects
http://code.google.com/p/lilypond/issues/detail?id=1451
See also issue 155 and issue 868.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mail
Comment #1 on issue 1451 by pnorcks: \parenthesize should enclose entire
objects
http://code.google.com/p/lilypond/issues/detail?id=1451
(No comment was entered for this change.)
Attachments:
parenthesize.preview.png 669 bytes
___
bug-li
On Tue, Dec 14, 2010 at 8:04 AM, Phil Holmes wrote:
> "Janek Warchoł" wrote in message
> news:aanlktik6jejyyemedv9zevfehs1nhz6ucupjguuwv...@mail.gmail.com...
>>
>> % I was very happy to find out that \parenthesize works not only with
>> notes,
>> but very unhappy to find out that the brackets see
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 1451 by pnorcks: \parenthesize should enclose entire objects
http://code.google.com/p/lilypond/issues/detail?id=1451
Original report:
http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00386.html
Parenthesis
Updates:
Labels: -fixed_2_13_41 fixed_2_13_3
Comment #4 on issue 810 by pnorcks: Improving tablatures support (rhythm
notation, etc.)
http://code.google.com/p/lilypond/issues/detail?id=810
Oops, sorry for the confusion...
___
bug-lilypond
Updates:
Labels: -fixed_2_13_3 fixed_2_13_41
Comment #3 on issue 810 by pnorcks: Improving tablatures support (rhythm
notation, etc.)
http://code.google.com/p/lilypond/issues/detail?id=810
This appears to have landed in 2.13.41.
___
bug-li
Updates:
Status: Verified
Comment #2 on issue 1437 by PhilEHolmes: [PATCH] Doc: Remove fragment
option from @lilypond LM
http://code.google.com/p/lilypond/issues/detail?id=1437
(No comment was entered for this change.)
___
bug-lilypond mai
Comment #2 on issue 1386 by PhilEHolmes: Tied harmonics in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=1386
Merged with which issue?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Updates:
Status: Verified
Comment #4 on issue 1344 by PhilEHolmes: [Patch:] Corrections in
notation/spacing.itely
http://code.google.com/p/lilypond/issues/detail?id=1344
(No comment was entered for this change.)
___
bug-lilypond mailing li
Updates:
Status: Verified
Comment #5 on issue 1299 by PhilEHolmes: ly/gregorian.ly needs
minimum-Y-extent updated
http://code.google.com/p/lilypond/issues/detail?id=1299
Checked and seen to be changed as discussed
___
bug-lilypond mailing
Updates:
Status: Verified
Comment #2 on issue 1275 by PhilEHolmes: name+email for lily-git.tcl
http://code.google.com/p/lilypond/issues/detail?id=1275
Verified. Worked for me when I first ran it.
___
bug-lilypond mailing list
bug-lilypond@gn
Updates:
Status: Verified
Comment #7 on issue 1028 by PhilEHolmes: Test failure when built without a
controlling tty
http://code.google.com/p/lilypond/issues/detail?id=1028
Since we do have a build .37, we must assume that this is OK.
___
"Graham Percival" wrote in message
news:aanlkti=yz=e4g8t0-sewrtxzyqgejmn3hbepeswsl...@mail.gmail.com...
On Tue, Dec 14, 2010 at 3:52 PM, Phil Holmes wrote:
"Phil Holmes" wrote in message
news:id2jug$48...@dough.gmane.org...
>>
>> Please see the attached output from the 13.40 regtests. There's
Status: Accepted
Owner:
Labels: Type-Collision Priority-Low
New issue 1450 by PhilEHolmes: Collision between slur and text in
les-nereides regtest
http://code.google.com/p/lilypond/issues/detail?id=1450
In the regtest les-nereides.ly, the slur on the first line collides with
text on th
On Tue, Dec 14, 2010 at 3:52 PM, Phil Holmes wrote:
> "Phil Holmes" wrote in message
> news:id2jug$48...@dough.gmane.org...
>>
>> Please see the attached output from the 13.40 regtests. There's a
>> collision
>> between the slur in the top staff and the figured bass numbering (?) in
>> the
>> se
"Janek Warchoł" wrote in message
news:aanlktik6jejyyemedv9zevfehs1nhz6ucupjguuwv...@mail.gmail.com...
% I was very happy to find out that \parenthesize works not only with
notes,
but very unhappy to find out that the brackets seem to have constant size.
For example, they are too small for chord
Updates:
Status: Fixed
Labels: fixed_2_13_43
Comment #1 on issue 1437 by percival.music.ca: [PATCH] Doc: Remove fragment
option from @lilypond LM
http://code.google.com/p/lilypond/issues/detail?id=1437
This was pushed a while ago.
wrote in message news:87eiam1vkq@notam02.no...
"D" == Dmytro O Redchuk writes:
D> Actually, i can understand why this output is _wanted_, but can
D> not imagine good Summary for issue report.
D> "Rest in lower voice should be placed above notes in in upper if
D> voices are cro
"Phil Holmes" wrote in message
news:id2jug$48...@dough.gmane.org...
Please see the attached output from the 13.40 regtests. There's a
collision
between the slur in the top staff and the figured bass numbering (?) in
the
second staff. Do collisions of this sort count as bugs?
Bump
--
Phil
Updates:
Status: Fixed
Labels: fixed_2_13_43
Comment #33 on issue 1336 by percival.music.ca: skipTypesetting segfaults
when set during a skipBars-induced MultiMeasureRest spanner
http://code.google.com/p/lilypond/issues/detail?id=1336
I've pushed Neil's patch. Thanks so much
Updates:
Status: Fixed
Labels: fixed_2_13_43
Comment #5 on issue 1440 by percival.music.ca: \book(part) containing
page-marker as only element segfaults
http://code.google.com/p/lilypond/issues/detail?id=1440
Pushed your patch
___
Updates:
Status: Fixed
Labels: fixed_2_13_42
Comment #1 on issue 1386 by v.villenave: Tied harmonics in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=1386
Merged.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http:/
Updates:
Status: Verified
Labels: fixed_2_13_42
Comment #2 on issue 1339 by v.villenave: [PATCH]Tablature: proper support
for tie/slur- and tie/glissando-constellations (issue2191042)
http://code.google.com/p/lilypond/issues/detail?id=1339
Merged.
___
Updates:
Status: Verified
Labels: fixed_2_13_42
Comment #1 on issue 1366 by v.villenave: [Patch] Tablature: proper support
for tie/slur- and tie/glissando-constellations
http://code.google.com/p/lilypond/issues/detail?id=1366
Merged.
_
On Tue 14 Dec 2010, 12:04 I wrote:
> On Thu 11 Nov 2010, 12:04 Xavier Scheuer wrote:
> > Hi!
> Hi, Xavier!
>
> > I know that NR 2.1 have been recently (is currently being?) improved.
> > I looked only at the latest _online_ (i.e. not git) version (2.13.39
> > at kainhofer.com), so please excuse me
On Thu 11 Nov 2010, 12:04 Xavier Scheuer wrote:
> Hi!
Hi, Xavier!
> I know that NR 2.1 have been recently (is currently being?) improved.
> I looked only at the latest _online_ (i.e. not git) version (2.13.39
> at kainhofer.com), so please excuse me if what I'm talking about has
> been already mod
On Wed 17 Nov 2010, 00:06 Xavier Scheuer wrote:
> Hi,
Hi!
> OK, this may be related to issue #1309 or more probably to #127 .
> This is not a regression from 2.12.3.
>
> %% I would have expected the second "ossia" to be right under the
> %% normal staff. Instead it is shifted below, like if the
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1449 by brownian.box: Killed staves affect vertical spacing
http://code.google.com/p/lilypond/issues/detail?id=1449
Reported by Xavier Scheuer,
http://lists.gnu.org/archive/html/bug-lilypond/2010-11/msg00243.html :
%
> I am not top posting.
The snipped below shows a small note head even in the Tab Staff where a
fret number should appear.
\version "2.13.42"
noteTrills = \relative c' {
\pitchedTrill c2\startTrillSpan d bes2\stopTrillSpan
}
\score {
<<
\new Staff {
\new Voice {
\noteTrill
55 matches
Mail list logo
