Comment #11 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
I've also added a --glob-input option (i.e. --glob-input=*.ly) to
lys-to-doc.py, but that didn't help because $(COLLATED_FILES) is a bunch of
filenames rather th
Updates:
Status: Fixed
Labels: Fixed_2_15_9
Comment #3 on issue 1699 by colinpkc...@gmail.com: Automated numbering for
footnotes
http://code.google.com/p/lilypond/issues/detail?id=1699
Pushed as 181366ec566a338c265ff4960724202d0d55ef79.
Cheers,
MS
Updates:
Status: Fixed
Labels: Fixed_2_15_9
Comment #5 on issue 1114 by colinpkc...@gmail.com: A later note's stem can
be to the left of an earlier note's stem
http://code.google.com/p/lilypond/issues/detail?id=1114
Pushed as aaacb8cdd5bc029a8d0c87f90b817d97fcd5ad80. Thanks t
On Aug 29, 2011, at 7:07 PM, lilyp...@googlecode.com wrote:
>
> Comment #7 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
> space after first system
> http://code.google.com/p/lilypond/issues/detail?id=1828
>
> I pushed the simple version only affecting the current context as
Comment #19 on issue 442 by joenee...@gmail.com: Enhancement:
RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
Or remove the Keep_alive_together engraver from PianoStaff.
___
b
Comment #19 on issue 804 by k-ohara5...@oco.net: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
I would not find the further changes of patch 4 to be helpful. The next
step on this issue, I think, is to wait f
Comment #18 on issue 442 by k-ohara5...@oco.net: Enhancement:
RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
if i need the old behaviour?
Use GrandStaff instead of PianoStaff for cases when you want LilyPond to
redu
Comment #5 on issue 1839 by lemzw...@googlemail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
Definitely an improvement! However, compared to the facsimile, the hollow
head of the semibrevis is a bit too `steep'. What about other facsimile
Comment #7 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
I pushed the simple version only affecting the current context as commit
2dad7be345ca1f4c04e836a56a9a66c0e340b39b
. If this leads to
Comment #4 on issue 1839 by paconet@gmail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
Much better, IMHO.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listin
Comment #3 on issue 1839 by bordage@gmail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
I made a new patch set. There is still a lot of work, but you can see in
the attached PNGs what has been done.
Feel free to criticize.
Thanks,
Bert
Comment #6 on issue 1828 by n.putt...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
That would be the same as \set stringTunings I should think
Yeah, you're absolutely right.
_
Comment #5 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
So anyway, I'd just use the following instead of overengineering. If you
are in a subcontext of some staff, your tough luck. Things
Comment #4 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
That would be the same as \set stringTunings I should think, and the
problem is exactly that the bottom context, once the music has st
Comment #3 on issue 1828 by n.putt...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Use the Bottom alias?
\set Bottom. stringTunings
Of course, if there's no TabStaff then you encounter the same problem.
_
Comment #2 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Perhaps I am thinking too complicated. Since one gives the tuning a name,
this command would likely be used right in the start of the
Comment #1 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Well, obviously one should not be setting values in non-existent contexts
since Lilypond then creates them. Ugh. I have the suspicio
Comment #56 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Apart from using lily-dev, now that lilyo-net is back on the air, the
instructions in CG 4.2 worked well for me on my Ubuntu machines.
Updates:
Status: Accepted
Labels: -Priority-Low
Comment #6 on issue 720 by percival.music.ca: incorrect bbox values for EPS
images
http://code.google.com/p/lilypond/issues/detail?id=720
we no longer do priorities, so that's beside the point.
I agree that the pdf bbox is incor
Comment #5 on issue 720 by lemzw...@googlemail.com: incorrect bbox values
for EPS images
http://code.google.com/p/lilypond/issues/detail?id=720
Well, I now see the opposite in the current manual. Cf.
http://lilypond.org/doc/v2.15/Documentation/notation/displaying-pitches#automatic-accidenta
Updates:
Status: Verified
Comment #16 on issue 746 by brownian.box: Automatic code indentation
improvement (and replacing tabs with spaces)
http://code.google.com/p/lilypond/issues/detail?id=746
Thank you.
___
bug-lilypond mailing list
bug
Comment #15 on issue 746 by percival.music.ca: Automatic code indentation
improvement (and replacing tabs with spaces)
http://code.google.com/p/lilypond/issues/detail?id=746
4a401ca1c60f428daa242dbdd102fdb3f327ebfb
___
bug-lilypond mailing list
bu
Updates:
Labels: -Priority-Medium fixed_2_15_9
Comment #9 on issue 40 by percival.music.ca: collision glissando accidental
(includes workaround)
http://code.google.com/p/lilypond/issues/detail?id=40
yes
___
bug-lilypond mailing list
bug-li
Comment #55 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I've just ordered a new PC which I'm going to install Ubuntu onto, and I'm
planning to use these instructions:
http://lilypond.org
Comment #18 on issue 804 by reinhold...@gmail.com: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
Comment #14 was about that one last warning on 32-bit systems mentioned in
comment #13. Since I don't have a 64
Comment #54 on issue 1635 by paconet@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
What required program are you asked to install? if it is fontforge, I run
Ubuntu and had the same problem. Uninstall fontforge, compile
Comment #53 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I am running ubuntu linux. Well, I did not try to get it working yet. Thank
you, I feel like I'll ask you for some help, if I fail to get it worki
Comment #17 on issue 804 by brownian.box: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
Sorry, I've misunderstood your comment (c#14).
___
bug-lilypond mailing list
Comment #52 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
What system are you running?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
Updates:
Status: Accepted
Comment #16 on issue 804 by reinhold...@gmail.com: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
That patch only fixes all warnings on 32 bit systems. Purportedly (and
that's
Updates:
Status: Verified
Comment #51 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Yes, I have an up to date git, but I can not pass configure stage, I've
got "please install required programs".
Comment #5 on issue 1795 by philehol...@googlemail.com: Improve handling of
languages in doc and website build
http://code.google.com/p/lilypond/issues/detail?id=1795
For the record - the 2nd patch at http://codereview.appspot.com/4964041/ is
an initial attempt to fix this, but needs better
Comment #8 on issue 40 by brownian.box: collision glissando accidental
(includes workaround)
http://code.google.com/p/lilypond/issues/detail?id=40
Should be tagged as "fixed_2_15_9" ?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://list
Updates:
Status: Verified
Comment #4 on issue 720 by brownian.box: incorrect bbox values for EPS
images
http://code.google.com/p/lilypond/issues/detail?id=720
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lily
Comment #50 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Sorry, Dmytro, it was done ages ago and I don't have a record. If you have
an up to date git, run "make website" and if you have no
Updates:
Status: Verified
Comment #15 on issue 804 by brownian.box: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
(No comment was entered for this change.)
_
Comment #5 on issue 1295 by brownian.box: Support for Mac OSX
10.3.9 "Panther" is broken
http://code.google.com/p/lilypond/issues/detail?id=1295
Why "Fixed"? Shouldn't it be "Invalid"?
Mmm.. What is better? -- "fixed, because we do not support" or "invalid,
because we do not support"?
_
Updates:
Status: Verified
Comment #27 on issue 1349 by brownian.box: Guile 2.0 compat: Scheme macros
must be defined/autocompiled before they are used.
http://code.google.com/p/lilypond/issues/detail?id=1349
Thanks for commit id.)
___
bug-
Comment #49 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Please, which commit ID?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mail
Comment #14 on issue 746 by brownian.box: Automatic code indentation
improvement (and replacing tabs with spaces)
http://code.google.com/p/lilypond/issues/detail?id=746
Please, fixed with which commit ID? Thanks.
___
bug-lilypond mailing list
bug-
Patrick
Thanks for raising this, but it is a known problem, see
http://code.google.com/p/lilypond/issues/detail?id=216.
Do actually need different scores to have different
spacing?
Trevor
- Original Message -
From: "Patrick Karl"
To:
Sent: Saturday, August 27, 2011 3:26 AM
Subject:
41 matches
Mail list logo
