Updates:
Labels: -Patch-new Patch-needs_work
Comment #50 on issue 1663 by pkx1...@gmail.com: Images missing on web site
http://code.google.com/p/lilypond/issues/detail?id=1663
Graham,
This fails at the basic make stage
../configure ; make -j7
I also re-ran make multiple times to see i
Comment #14 on issue 1526 by percival.music...@gmail.com: Building only
English docs
http://code.google.com/p/lilypond/issues/detail?id=1526
I agree with #3 as a general rule. I agree that #1 is easily solved by
just typing more and that's no issue for unix people; I'm not certain that
I
Updates:
Labels: Patch-review
Comment #1 on issue 1974 by percival.music...@gmail.com: Fix the 404 on
contributor-big-page and contributor/website-build
http://code.google.com/p/lilypond/issues/detail?id=1974#c1
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #6 on issue 1917 by percival.music...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917#c6
Patchy the autobot says: LGTM.
___
bug-lilypond m
Comment #13 on issue 1526 by julien.r...@gmail.com: Building only English
docs
http://code.google.com/p/lilypond/issues/detail?id=1526
I might look intoimplementing `make html-doc' and `make pdf-doc' or
something like that as those to me seem to warrant some special targets.
Comment #12 on issue 1526 by julien.r...@gmail.com: Building only English
docs
http://code.google.com/p/lilypond/issues/detail?id=1526
If I'm picking my answer there would be no patch because I would stick to
the `make this-file' idiom. Special targets like `make doc' are available
and th
Updates:
Labels: Patch-new
Comment #5 on issue 1917 by percival.music...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917
(No comment was entered for this change.)
___
bug-lilyp
Comment #4 on issue 1917 by julien.r...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917#c4
Fix hyperlinks on web-big-page (issue 1917).
This patch is about the current issue (got it right this time).
http://codereview.appspot.co
Comment #11 on issue 1526 by percival.music...@gmail.com: Building only
English docs
http://code.google.com/p/lilypond/issues/detail?id=1526
"windows users running lilydev". Yes, they have ubuntu, but they're still
unfamiliar with the process.
I already know that
make out=www build/Doc
Comment #10 on issue 1526 by julien.r...@gmail.com: Building only English
docs
http://code.google.com/p/lilypond/issues/detail?id=1526
I'm puzzled how you run this build system on windows. Doesn't it rely on
tons of shell utilities? sed ls ln grep tail what have you?
Anyway, yes sure ease
Comment #9 on issue 1526 by julien.r...@gmail.com: Building only English
docs
http://code.google.com/p/lilypond/issues/detail?id=1526
It's true that I'm building in source to test this, but if your build
system is only half-broken it shouldn't matter if you do that
out-of-source. Worth gi
Updates:
Labels: -Priority-Medium
Comment #8 on issue 1526 by percival.music...@gmail.com: Building only
English docs
http://code.google.com/p/lilypond/issues/detail?id=1526
We heavily discourage in-tree builds; inexperienced contributors should
always be doing out-of-tree builds in
paconet.org wrote:
>
>
> To reuse existing lyrics contexts -- how clever!
>
>
thanks - just added http://lsr.dsi.unimi.it/LSR/Item?u=1&id=781
--
View this message in context:
http://old.nabble.com/wrong-alignment-when-repeating-music-with-different-text-on-one-line-tp32622828p32671196.html
Comment #7 on issue 1526 by julien.r...@gmail.com: Building only English
docs
http://code.google.com/p/lilypond/issues/detail?id=1526
Presuming you're currently working in Documentation/
To build English-only docs:
make local-doc
When you recently did make local-doc and have up-to-date pdf'
Updates:
Cc: pkx1...@gmail.com
Comment #49 on issue 1663 by percival.music...@gmail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
James, could you test this one with a full doc build? Google only gives
patchy the first 25 comments, so he's
Updates:
Labels: Patch-review
Comment #3 on issue 983 by percival.music...@gmail.com: relative location
of css/ and pictures/ dir
http://code.google.com/p/lilypond/issues/detail?id=983#c3
Patchy the autobot says: LGTM.
___
bug-lilypond mai
Updates:
Labels: Patch-review
Comment #7 on issue 1972 by percival.music...@gmail.com: Seg fault and 100%
CPU when using \override Staff.StaffSymbol #'ledger-positions
http://code.google.com/p/lilypond/issues/detail?id=1972#c7
Patchy the autobot says: LGTM.
_
Updates:
Labels: Patch-review
Comment #5 on issue 1952 by percival.music...@gmail.com: Patch: Sketch for
broken beams with consistent slopes
http://code.google.com/p/lilypond/issues/detail?id=1952#c5
Patchy the autobot says: LGTM.
___
bug-
Comment #3 on issue 1917 by percival.music...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917
meh, issue numbers are cheap. Spun off as issue 1974.
___
bug-lilypond mailing list
bug-l
Status: Accepted
Owner:
Labels: Type-Build Patch-new
New issue 1974 by percival.music...@gmail.com: Fix the 404 on
contributor-big-page and contributor/website-build
http://code.google.com/p/lilypond/issues/detail?id=1974
They were actually excluded in the www_post processing stage becau
Comment #2 on issue 1917 by julien.r...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917
I just reread the description of the bug, and the patch that I just posted
is actually for a different bug, sorry about that. The patch addr
Comment #6 on issue 1972 by percival.music...@gmail.com: Seg fault and 100%
CPU when using \override Staff.StaffSymbol #'ledger-positions
http://code.google.com/p/lilypond/issues/detail?id=1972
Patch location: (newlines requried for now; please use our updated git-cl)
http://codereview.apps
Comment #1 on issue 1917 by julien.r...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917#c1
Fix the 404 on contributor-big-page and contributor/website-build (issue
1917).
They were actually excluded in the www_post processing
Updates:
Labels: -Patch-review Patch-countdown
Comment #9 on issue 1951 by percival.music...@gmail.com: Scripts collide
with accidentals
http://code.google.com/p/lilypond/issues/detail?id=1951
(No comment was entered for this change.)
___
Updates:
Labels: Patch-new
Comment #5 on issue 1972 by percival.music...@gmail.com: Seg fault and 100%
CPU when using \override Staff.StaffSymbol #'ledger-positions
http://code.google.com/p/lilypond/issues/detail?id=1972
(No comment was entered for this change.)
Updates:
Labels: Patch-needs_work
Comment #20 on issue 1110 by percival.music...@gmail.com: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
I'm needs_work'ing this so we don't lose the patch.
__
Updates:
Labels: Patch-new
Comment #2 on issue 983 by percival.music...@gmail.com: relative location
of css/ and pictures/ dir
http://code.google.com/p/lilypond/issues/detail?id=983
(No comment was entered for this change.)
___
bug-lilypon
Updates:
Labels: Patch-new
Comment #47 on issue 1663 by percival.music...@gmail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Labels: -Patch-review Patch-push
Comment #22 on issue 1926 by percival.music...@gmail.com: 2.15.12
processing speed problems
http://code.google.com/p/lilypond/issues/detail?id=1926
just push it, since it's been through a review
__
Comment #4 on issue 1972 by piersti...@gmail.com: Seg fault and 100% CPU
when using \override Staff.StaffSymbol #'ledger-positions
http://code.google.com/p/lilypond/issues/detail?id=1972
There is a patch at Rietveld: http://codereview.appspot.com/4974075/
___
Comment #19 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
I've made a minimal proof-of-concept sketch on
http://codereview.appspot.com/5286048>. It only works on music
sequences, and
2011/10/17 -Eluze :
> yes - but the problem is when they are on the same line!
>
> here is a solution to the problem you mention above. it obviously prevents
> the lyrics contexts to die:
>
> \score {
> <<
> \new Staff \music
> \new Lyrics = "line1"
> \new Lyrics = "line2"
> \context L
Comment #1 on issue 983 by julien.r...@gmail.com: relative location of css/
and pictures/ dir
http://code.google.com/p/lilypond/issues/detail?id=983#c1
Centralize the css files and fix the links to css files (issue 983).
Put them in Documentation/css.
http://codereview.appspot.com/5285053
paconet.org wrote:
>
> 2011/10/16 -Eluze :
>>
>>
>> Phil Holmes-2 wrote:
>>>
>>> This looks to me like correct behaviour. You've created extra Lyrics
>>> contexts, and Lilypond stacks them one above the other. This is as
>>> illustrated in the NR. If I was doing what you're showing, I would u
Comment #46 on issue 1663 by julien.r...@gmail.com: Images missing on web
site
http://code.google.com/p/lilypond/issues/detail?id=1663#c46
Fix the links to music samples in web-big-page (issue 1663).
We move all of Documentation/web/ly-examples to Documentation/ly-examples
and rework the lin
Updates:
Status: Fixed
Comment #11 on issue 509 by mts...@gmail.com: collision nested tuplet
numbers
http://code.google.com/p/lilypond/issues/detail?id=509
Pushed with 2bf0066ec032cdea3897dd66145c752b82ccb865.
___
bug-lilypond mailing list
On Oct 17, 2011, at 1:12 PM, m...@apollinemike.com wrote:
> On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
>
>> On 17 October 2011 11:41, Graham Percival wrote:
>>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
On 17 Oct 2011 07:56, "Peekay Ex" wrote:
> However
Keith OHara wrote:
>
> -Eluze gmail.com> writes:
>> Luke Bakken wrote:
>> > After running installer, system PATH was clobbered and only had
>> Lilypond
>> > path in
>> > it. See attached screenshot.
>> >
>> the semi-colon at the beginning of the field named "variable value" is a
>> strong ind
Updates:
Labels: -Patch-needs_work Patch-new
Comment #4 on issue 1952 by mts...@gmail.com: Patch: Sketch for broken
beams with consistent slopes
http://code.google.com/p/lilypond/issues/detail?id=1952
Hey all,
I'm patch-newing this because I decided to make some changes before pushin
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On 17 October 2011 11:41, Graham Percival wrote:
> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>
>> > However, and this is for Phil: could we not simply 'deprecate' the
>> > snippet(s) like we do with any that won't work (properly) in
On Mon, Oct 17, 2011 at 08:22:54AM +0200, m...@apollinemike.com wrote:
> I think that there is an issue with file-touchability. Certain snippets in
> the docs are not editable,
Not editable by hand, you mean. convert-ly is still fine.
> and the convert-ly rules don't know how to handle this in
On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>
> > However, and this is for Phil: could we not simply 'deprecate' the
> > snippet(s) like we do with any that won't work (properly) in later
> > versions, and actually I think it was Mike t
2011/10/16 -Eluze :
>
>
> Phil Holmes-2 wrote:
>>
>> This looks to me like correct behaviour. You've created extra Lyrics
>> contexts, and Lilypond stacks them one above the other. This is as
>> illustrated in the NR. If I was doing what you're showing, I would use
>> \skip:
>>
>> <<
>> \new S
-Eluze gmail.com> writes:
> Luke Bakken wrote:
> > After running installer, system PATH was clobbered and only had Lilypond
> > path in
> > it. See attached screenshot.
> >
> the semi-colon at the beginning of the field named "variable value" is a
> strong indicator - if not the proof - that the
Updates:
Status: Fixed
Comment #1 on issue 1971 by mts...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
Fixed with 84fa3cb9de968a45ef1bd07e9fe96cec1f3eaf87.
___
bug-lilypond mailing list
bug-l
Comment #3 on issue 1972 by piersti...@gmail.com: Seg fault and 100% CPU
when using \override Staff.StaffSymbol #'ledger-positions
http://code.google.com/p/lilypond/issues/detail?id=1972
I'll have a look at it, and add a warning or error messages in case
something is strange.
Sorry for th
Luke Bakken wrote:
>
> lilypond-2.14.2-1.mingw.exe
>
> Windows 7 SP1
>
> After running installer, system PATH was clobbered and only had Lilypond
> path in
> it. See attached screenshot.
>
> …
>
> See http://code.google.com/p/lilypond/issues/detail?id=1948
>
the semi-colon at the beginning
Comment #3 on issue 1962 by brownian@gmail.com: Visible gap in span bar
when making lyrics to avoid bar lines
http://code.google.com/p/lilypond/issues/detail?id=1962
C#2> Also if you comment out just one (any one)
Not exactly. Commenting out 'transparent = ##t makes the space almost
inv
On Oct 17, 2011, at 9:30 AM, Peekay Ex wrote:
> Mike
>
> On Mon, Oct 17, 2011 at 8:12 AM, m...@apollinemike.com
> wrote:
>> On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
>>
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate'
Mike
On Mon, Oct 17, 2011 at 8:12 AM, m...@apollinemike.com
wrote:
> On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
>
>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>
>>> However, and this is for Phil: could we not simply 'deprecate' the
>>> snippet(s) like we do with any that won't work (proper
On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>
>> However, and this is for Phil: could we not simply 'deprecate' the
>> snippet(s) like we do with any that won't work (properly) in later
>> versions, and actually I think it was Mike that a week or s
On 17 Oct 2011 07:56, "Peekay Ex" wrote:
> However, and this is for Phil: could we not simply 'deprecate' the
> snippet(s) like we do with any that won't work (properly) in later
> versions, and actually I think it was Mike that a week or so ago
> pointed one out to me that was deprecated as of 2
Comment #2 on issue 1962 by pkx1...@gmail.com: Visible gap in span bar when
making lyrics to avoid bar lines
http://code.google.com/p/lilypond/issues/detail?id=1962
If it helps if you use
\new Lyrics \lyricsto "voice" {
\lyricmode { " " }
}
Then you don't get the space.
Also if you
55 matches
Mail list logo
