Comment #4 on issue 2177 by lemzw...@gmail.com: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177
No, it isn't. Removing a header file doesn't automatically trigger the
engine to update the *.dep files.
In groff (which I maintain)
lilypond-4 wrote:
>
> Status: Accepted
> Owner:
> Labels: Type-Enhancement
>
> New issue 2192 by lemzw...@gmail.com: tighter polyphony
> http://code.google.com/p/lilypond/issues/detail?id=2192
>
> The attached image shows rather large horizontal distances between the
> voices (this setu
Comment #4 on issue 2134 by gra...@percival-music.ca: Redirect old website
/ download to new location
http://code.google.com/p/lilypond/issues/detail?id=2134
something along the above patch may be used eventually, but I guess you
could consider this issue as being blocked on other work.
I
Status: Accepted
Owner:
New issue 2193 by lemzw...@gmail.com: collision between beams and rests
http://code.google.com/p/lilypond/issues/detail?id=2193
\version "2.15.24"
\header { texidoc = "
Bars and rests from different voices shouldn't collide.
Here is a counterexample, which is a reg
Comment #3 on issue 2177 by gra...@percival-music.ca: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177
how on earth do I do that?
I suspected a build problem, so patchy now re-runs autogen.sh and
configure. That isn't enough to reg
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2192 by lemzw...@gmail.com: tighter polyphony
http://code.google.com/p/lilypond/issues/detail?id=2192
The attached image shows rather large horizontal distances between the
voices (this setup is necessary e.g. for Bach's Chaconne
Comment #2 on issue 2177 by lemzw...@gmail.com: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177
This is a problem with patchy: After applying a patch, all *.dep files
should be regenerated. The patch itself works fine, BTW, at least
Status: Started
Owner: pkx1...@gmail.com
Labels: Type-Enhancement Patch-new
New issue 2191 by pkx1...@gmail.com: Web: update to version 2.15, use it in
the "site:" part
http://code.google.com/p/lilypond/issues/detail?id=2191
Patch from
Pavel Roskin
Doc search: update to version 2.15, use it
Comment #3 on issue 2134 by pkx1...@gmail.com: Redirect old website /
download to new location
http://code.google.com/p/lilypond/issues/detail?id=2134
Graham/Alberto I'm not sure about this issue now, I see the tracker has
been 'closed' after Alberto's last 'comment' in
http://codereview.
Comment #26 on issue 1943 by c_soren...@byu.edu: lilypond after 2.15.8
fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Christian,
What did you to to make these run? I'd like to get the appropriate
commands in GUB so that the OS/X releases work properly.
Thanks,
Updates:
Labels: Patch-needs_work
Comment #1 on issue 2177 by lilypond...@gmail.com: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177#c1
Patchy the autobot says: no rule to make column-description.hh needed by
simple-spacer
Updates:
Labels: Patch-review
Comment #3 on issue 2189 by lilypond...@gmail.com: Doc: NR add to \partial
for clearer understanding
http://code.google.com/p/lilypond/issues/detail?id=2189#c3
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-needs_work
Comment #4 on issue 2188 by lilypond...@gmail.com: Patch: Turns beam
translation into a callback.
http://code.google.com/p/lilypond/issues/detail?id=2188#c4
Patchy the autobot says: tons of warnings and stem-tremolo-staff-space.ly
looks silly
___
Comment #22 on issue 2149 by plros...@gmail.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
\bikeshedOn
In my experience, negation is a distraction for human mind. As a C
programmer, I strive to use "HAVE_FOO" rather than "HAVE_
Comment #12 on issue 586 by plros...@gmail.com: Cross-staff slur causes a
weird output
http://code.google.com/p/lilypond/issues/detail?id=586
I don't think there is any bug that puts the slur start on the wrong
staff. Try adding this:
#(set-global-staff-size 20)
Now change the number gra
On Jan 6, 2012, at 10:49 PM, Trevor Daniels wrote:
>
>> Comment #13 on issue 1933 by m...@apollinemike.com: Lilypond-book requires
>> msvcrt again
>> http://code.google.com/p/lilypond/issues/detail?id=1933
>>
>> I think I may have found a one-stop-shopping solution to most of these
>> problems:
Comment #13 on issue 1933 by m...@apollinemike.com: Lilypond-book requires
msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933
I think I may have found a one-stop-shopping solution to most of these
problems:
http://python-mingw.donbennett.org:8081/mywiki/Installation
Mike
Comment #13 on issue 1933 by m...@apollinemike.com: Lilypond-book requires
msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933
I think I may have found a one-stop-shopping solution to most of these
problems:
http://python-mingw.donbennett.org:8081/mywiki/Installation
It
2012/1/1 Chris Morgan
> On Sun, Jan 1, 2012 at 1:01 AM, James wrote:
>
> > > \markup { Here is how beamed quaver tuplets look now; ugly, with some
> > colliding
> > > with the staff lines: }
>
This has been added as
http://code.google.com/p/lilypond/issues/detail?id=2190
Thank you for report.
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2190 by ma...@gregoriana.sk: Tuplet positioning on beamed notes
is ugly
http://code.google.com/p/lilypond/issues/detail?id=2190
http://lists.gnu.org/archive/html/bug-lilypond/2011-12/msg01116.html
\version "2.15.23" % also 2.14.2
\mark
Comment #30 on issue 1948 by m...@apollinemike.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
mingw .exe will be uploaded in about 5 minutes.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Updates:
Labels: Patch-new
Comment #2 on issue 2189 by pkx1...@gmail.com: Doc: NR add to \partial for
clearer understanding
http://code.google.com/p/lilypond/issues/detail?id=2189#c2
Doc: NR Section on Upbeats made clearer
Tracker issue 2189
Created simpler and clearer @lilypond ex
Comment #1 on issue 2189 by d...@gnu.org: Doc: NR add to \partial for
clearer understanding
http://code.google.com/p/lilypond/issues/detail?id=2189
I don't think the wording is significantly clearer. It is a good idea to
avoid "interval" since that has a different meaning in music, but I'
Updates:
Labels: Patch-new
Comment #29 on issue 1948 by pkx1...@gmail.com: Windows install clobbered
system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948#c29
Doc: Usage - added link for Windows users
This is part of Tracker 1948
The Document now links to the installat
Updates:
Summary: git-cl doesn't 'always' remember (the last) tracker issue number
you used
Labels: -Type-Git-cl Type-Scripts git-cl
Comment #1 on issue 2187 by pkx1...@gmail.com: git-cl doesn't 'always'
remember (the last) tracker issue number you used
http://code.google.com/p/lil
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2189 by pkx1...@gmail.com: Doc: NR add to \partial for clearer
understanding
http://code.google.com/p/lilypond/issues/detail?id=2189
Laura Conrad lcon...@laymusic.org via gnu.org
to lilypond-user
"David" == David Kastrup
Comment #28 on issue 1948 by m...@apollinemike.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
On it.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-
Comment #27 on issue 1948 by philehol...@gmail.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
As promised, a patch for GUB. Could someone who has this working download
and apply this, please? The outcome should be that PATH is unchanged
Comment #26 on issue 1948 by philehol...@gmail.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
I'll make a GUB patch and post it here.
James added this to the discussion:
"If you look here:
http://lilypond.org/doc/v2.14/Documentation/usage
Comment #3 on issue 2188 by lemzw...@gmail.com: Patch: Turns beam
translation into a callback.
http://code.google.com/p/lilypond/issues/detail?id=2188
beam-distance?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/
Comment #2 on issue 2188 by m...@apollinemike.com: Patch: Turns beam
translation into a callback.
http://code.google.com/p/lilypond/issues/detail?id=2188
I agree - what would you suggest renaming it?
___
bug-lilypond mailing list
bug-lilypond@gnu.
Comment #1 on issue 2188 by lemzw...@gmail.com: Patch: Turns beam
translation into a callback.
http://code.google.com/p/lilypond/issues/detail?id=2188
LGTM. In this context I strongly suggest to better document (or even
rename) `length-fraction'.
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2188 by mts...@gmail.com: Patch: Turns beam translation into a
callback.
http://code.google.com/p/lilypond/issues/detail?id=2188
Turns beam translation into a callback.
http://codereview.appspot.com/5517055
__
Comment #21 on issue 2149 by d...@gnu.org: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
I have turned to the Guile manual for guidance about what would fit into
the scheme of names, and we have basically "length" as a textual
desc
Status: Accepted
Owner:
Labels: Type-Git-cl
New issue 2187 by janek.li...@gmail.com: git-cl doesn't remember tracker
issue number
http://code.google.com/p/lilypond/issues/detail?id=2187
If you tell git-cl to create a new tracker issue when uploading, it doesn't
remember the number of c
Status: Accepted
Owner:
Labels: Type-Git-cl
New issue 2186 by janek.li...@gmail.com: git-cl always uses first commit's
message
http://code.google.com/p/lilypond/issues/detail?id=2186
You wrote a patch, committed it and uploaded with git-cl - everything is
fine, commit message is displa
Comment #25 on issue 1948 by m...@apollinemike.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
I think that Phil's proposal is the best option - please make the patch.
___
bug-lilypond mailing lis
Comment #1 on issue 2184 by gra...@percival-music.ca: GUB can't download
netpbm
http://code.google.com/p/lilypond/issues/detail?id=2184
also necessary for
bin/gub tools::rsync
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.
On Wed, Jan 4, 2012 at 7:09 PM, Nick Payne wrote:
> On 05/01/12 07:58, Nick Payne wrote:
>
>> See below. If the note with the accidental appears first in the chord,
>> then the fingering for the other note correctly avoids the accidental. If
>> the order of the notes is reversed, the fingering col
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2185 by ralphbug...@gmail.com: Chord fingering placement request
http://code.google.com/p/lilypond/issues/detail?id=2185
This is more of an aesthetic question than a bug. Do we need further
discussion?
Nick Payne wrote :
I also think t
Status: Accepted
Owner:
Labels: Type-Critical
New issue 2184 by gra...@percival-music.ca: GUB can't download netpbm
http://code.google.com/p/lilypond/issues/detail?id=2184
the existing url is broken, which I'm going to fix in a minute or two. But
even with the right url, GUB doesn't auto
hello,
On 6 January 2012 11:23, wrote:
> On Fri, 6 Jan 2012 11:14:34 +, Graham Percival wrote:
>>
>> On Fri, Jan 06, 2012 at 10:21:19AM +, lilyp...@googlecode.com wrote:
>>>
>>>
>>> We'd need to be careful over that. Think it's no problem from a
>>> pure Lilypond perspective - I'd doubt
Comment #24 on issue 1948 by philehol...@gmail.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
Graham said:
Good point! Does anybody feel like checking into this?
I still think it's best to just explain which directories need to
be in the
Comment #11 on issue 2171 by m...@apollinemike.com: Patch: Implements
DOM-id property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
But I don't agree with your assessment that there was no reason to holler
in the first place.
I'm sorry if I gave this impression - I ce
Comment #10 on issue 2171 by d...@gnu.org: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
Mike: again, I am not proud of my performance here. But where is the point
of a review where the issue, the review description, and the code conta
On Fri, 6 Jan 2012 11:14:34 +, Graham Percival wrote:
On Fri, Jan 06, 2012 at 10:21:19AM +, lilyp...@googlecode.com
wrote:
We'd need to be careful over that. Think it's no problem from a
pure Lilypond perspective - I'd doubt many windows users would run
lily from the command line. How
On Fri, Jan 06, 2012 at 10:21:19AM +, lilyp...@googlecode.com wrote:
>
> We'd need to be careful over that. Think it's no problem from a
> pure Lilypond perspective - I'd doubt many windows users would run
> lily from the command line. However, I believe they would run -book
> from the comma
Comment #23 on issue 1948 by pkx1...@gmail.com: Windows install clobbered
system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
Suggest adding something in the Usage Manual then. Normally users would
look in usage for Lilypond-book right?
___
Comment #9 on issue 2171 by m...@apollinemike.com: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
If people would not consider it totally fine to just ignore every
standard we set up, I would not be appalled to a degree where I act in
Comment #22 on issue 1948 by philehol...@gmail.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
We'd need to be careful over that. Think it's no problem from a pure
Lilypond perspective - I'd doubt many windows users would run lily from the
Comment #8 on issue 2171 by d...@gnu.org: Patch: Implements DOM-id property
for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
I don't think it's good practice to unilaterally bounce patches from
staging based on one's personal opinion of the quality of the patch.
No, it i
Comment #2 on issue 2175 by janek.li...@gmail.com: Patch: explain how to
add git-cl to PATH
http://code.google.com/p/lilypond/issues/detail?id=2175#c2
explain how to add git-cl to PATH
i know modifying PATH is basic knowledge,
but i'm windows man and figuring this out
took me 15 minutes... t
Updates:
Status: Fixed
Comment #6 on issue 1629 by mts...@gmail.com: Tuplet line collides with
fingering
http://code.google.com/p/lilypond/issues/detail?id=1629
Pushed to staging as 929c7dbb51877dc11825a13e8a25456b2b14532a.
___
bug-lilypon
On Fri, Jan 06, 2012 at 09:37:51AM +, lilyp...@googlecode.com wrote:
>
> I don't think it's good practice to unilaterally bounce patches from
> staging based on one's personal opinion of the quality of the patch,
> especially when the patch has had a human LGTM from the best SVG
> developer on
Comment #7 on issue 2171 by m...@apollinemike.com: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
I don't think it's good practice to unilaterally bounce patches from
staging based on one's personal opinion of the quality of the patch,
Updates:
Status: Started
Comment #6 on issue 2171 by d...@gnu.org: Patch: Implements DOM-id property
for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Labels: -Patch-push Patch-review
Comment #5 on issue 2171 by d...@gnu.org: Patch: Implements DOM-id property
for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
WTF is this even for? There is no explanation whatsoever in the issue
description, there is no ex
Updates:
Status: Fixed
Comment #8 on issue 2165 by mts...@gmail.com: Patch: Modifies broken
hairpin height
http://code.google.com/p/lilypond/issues/detail?id=2165
Pushed to staging as 87a8ec69e1ef15aa6e18c11ec7d674ce46e0b5b7.
___
bug-lilyp
Updates:
Status: Fixed
Comment #20 on issue 2149 by mts...@gmail.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
Part of the patch pushed to staging as
6abea44be29f2de2abbc840507c9184132c8024d.
I'm gonna abandon the rest b
Updates:
Status: Fixed
Comment #4 on issue 2171 by mts...@gmail.com: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
Pushed to staging as 6abea44be29f2de2abbc840507c9184132c8024d.
___
bu
60 matches
Mail list logo
