As posted to lilypond-user, assertion of copyright in a score header has no
discernible effect on the output. I don’t much care where it ends up, but it
ought to do something. The attached tiny example was made with 2.12, but
apparently the problem persists in 2.14 and up.
[Er... I don’t seem to
Updates:
Status: Fixed
Labels: -Patch-new Fixed_2_15_27
Comment #2 on issue 2044 by julien.r...@gmail.com: convert-ly fails on
input with invalid version string
http://code.google.com/p/lilypond/issues/detail?id=2044
pushed 27ab4484f6a109758d0b5bc7194bfdeaa4abebaa
__
Updates:
Labels: Patch-new
Comment #1 on issue 2044 by julien.r...@gmail.com: convert-ly fails on
input with invalid version string
http://code.google.com/p/lilypond/issues/detail?id=2044#c1
convert-ly: Handle malformed \version string (issue 2044).
http://codereview.appspot.com/5563
Updates:
Labels: Patch-new
Comment #3 on issue 803 by julien.r...@gmail.com: correction needed for the
German translation of convert-ly
http://code.google.com/p/lilypond/issues/detail?id=803#c3
convert-ly: Better formatted error messages (issue 803).
http://codereview.appspot.com/556
Updates:
Status: Started
Comment #2 on issue 2056 by julien.r...@gmail.com: Typos in German
translation
http://code.google.com/p/lilypond/issues/detail?id=2056
pushed 36068080f58657b9e98172b5255f5a8905da5e9e to lilypond/translation
someone needs to upload the new Documentation/picture
On 21 Jan 2012, at 13:09, James wrote:
> Hello,
>
> On 21 January 2012 12:55, m...@apollinemike.com wrote:
>> On Jan 21, 2012, at 1:47 PM, Damian leGassick wrote:
>>
>>>
>>> On 21 Jan 2012, at 12:08, Damian leGassick wrote:
>>>
Hi
I've seen this before and a search through th
Comment #6 on issue 2240 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
The symptom would totally be what happens if
e8f544af29c93145d122efa8dcfc0548d9b84f0b is not present.
Try deleting lily/out/str
Updates:
Labels: -Patch-new Patch-needs_work
Comment #5 on issue 2240 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
Sorry, I tried it twice, checked git manually, deleted the old bui
Updates:
Status: Verified
Comment #39 on issue 1943 by gra...@percival-music.ca: lilypond after
2.15.8 fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
(No comment was entered for this change.)
___
bug-lilypond mai
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_27
Comment #38 on issue 1943 by gra...@percival-music.ca: lilypond after
2.15.8 fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
pushed.
___
bug-lilypon
Comment #27 on issue 2100 by janek.li...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100
thanks for your work, Carl and Graham!
___
bug-lilypond mailing list
bug-lilypond@gnu.
Updates:
Status: Started
Owner: mts...@gmail.com
Comment #37 on issue 1943 by carl.d.s...@gmail.com: lilypond after 2.15.8
fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
(No comment was entered for this change.)
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_27
Comment #26 on issue 2100 by carl.d.s...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100
Pushed to staging:
3ce31881e22216ea7b6b2c7f1cadaa9de6c5d
Updates:
Labels: -Type-Enhancement Type-Critical
Comment #4 on issue 2240 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
(No comment was entered for this change.)
__
Comment #3 on issue 2240 by mts...@gmail.com: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
You can change the description through edit issue on Rietveld.
___
bug-lilypond m
Updates:
Status: Started
Owner: d...@gnu.org
Comment #2 on issue 2240 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
The description is obviously no longer accurate: everything should wor
Issue 2239: google code only returns 20 or 25 comments with API
http://code.google.com/p/lilypond/issues/detail?id=2239
This issue is no longer blocking issue 2070.
See http://code.google.com/p/lilypond/issues/detail?id=2070
--
You received this message because you are listed in the owner
or CC f
Comment #1 on issue 2240 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
Issue 2070 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypon
Updates:
Status: Duplicate
Labels: -Patch-needs_work
Mergedinto: 2240
Blockedon: -2239
Comment #37 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Merging thi
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2240 by d...@gnu.org: Patch: Don't wrap EventChord around
rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2240
Don't wrap EventChord around rhythmic events by default.
This changes quite a num
Updates:
Labels: -Patch-new Patch-push
Comment #36 on issue 1943 by gra...@percival-music.ca: lilypond after
2.15.8 fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Doesn't make sense to have this on a countdown. I'll push it when I'm at
university this eve
Comment #25 on issue 2100 by gra...@percival-music.ca: Patch: CG:
explanation of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100
I think the notion of a "countdown" has played its part for this issue. I
suggest that we push it; the only remaining quibbles
Comment #35 on issue 1943 by mts...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
I've posted a patch.
Could I get git commit access to GUB so I can push this thing when (if) it
makes it through the countdown?
_
Updates:
Labels: Patch-new
Comment #34 on issue 1943 by mts...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943#c34
Adds new lilypad source
http://codereview.appspot.com/068
__
Comment #36 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
lilyp...@googlecode.com writes:
Hm. I deleted many comments now. If it is a total number problem, this
might help. If it is a
Issue 2239: google code only returns 20 or 25 comments with API
http://code.google.com/p/lilypond/issues/detail?id=2239
This issue is now blocking issue 2070.
See http://code.google.com/p/lilypond/issues/detail?id=2070
--
You received this message because you are listed in the owner
or CC fields
Updates:
Labels: -Patch-new Patch-needs_work
Blockedon: 2239
Comment #35 on issue 2070 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
oh, it's probably that problem where goog
Status: Accepted
Owner:
Labels: Type-Maintainability Frog
New issue 2239 by gra...@percival-music.ca: google code only returns 20 or
25 comments with API
http://code.google.com/p/lilypond/issues/detail?id=2239
when you ask for all comments via the googlecode API and/or the json
interfa
Hi,
Just upgraded from 2.12 to 2.14.2.
Problem:
Compiling the example below results in a waring in the log file:
Warnung: Keine Saite fuer Tonhoehe # (Bund (5) angegeben)
and the c note is lost.
However, that note was shown as the empty 4th string in 2.12.
\score {
\new TabStaff {
%
Comment #34 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
I don't think NR should be affected. The extending/programming reference
will likely need a few touchups, but not all that much
Comment #33 on issue 2070 by pkx1...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
David,
Do we need any ew @warnings added anywhere in the NR that you can think of
off the top of your head - in case this
Hi,
Just upgraded from 2.12 to 2.14.2.
Problem:
If an accord spans more than or equal to 2 octaves,
an empty string is not used but the lowest string shows a fretted position.
Example:
\score {
\new TabStaff {
< a, gis' >1
< a, a' >1
< a, ais' >1
Issue 2229: Patch: Broadcast articulations not in EventChord
http://code.google.com/p/lilypond/issues/detail?id=2229
This issue is no longer blocking issue 2070.
See http://code.google.com/p/lilypond/issues/detail?id=2070
--
You received this message because you are listed in the owner
or CC fiel
Updates:
Blockedon: -2229
Comment #32 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
If you are not working with song/festival or the XML output, this is pretty
much the final can
Updates:
Status: Fixed
Comment #4 on issue 2237 by pkx1...@gmail.com: Patch: Fix spelling in
input/regression/*.ly
http://code.google.com/p/lilypond/issues/detail?id=2237
author Stefan Weil
Thu, 19 Jan 2012 21:39:31 + (22:39 +0100)
committer
James Lowe
Sat, 21 Jan 2012
Updates:
Labels: Patch-new
Comment #31 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c31
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of th
Hello,
On 21 January 2012 12:55, m...@apollinemike.com wrote:
> On Jan 21, 2012, at 1:47 PM, Damian leGassick wrote:
>
>>
>> On 21 Jan 2012, at 12:08, Damian leGassick wrote:
>>
>>> Hi
>>>
>>> I've seen this before and a search through the list says it was fixed in
>>> 2.14
>>>
>>> just upgraded
On Jan 21, 2012, at 1:47 PM, Damian leGassick wrote:
>
> On 21 Jan 2012, at 12:08, Damian leGassick wrote:
>
>> Hi
>>
>> I've seen this before and a search through the list says it was fixed in 2.14
>>
>> just upgraded to 2.15.26 and i get
>>
>> GNU LilyPond 2.15.26
>> ERROR: In procedure pri
Comment #30 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Not when tested on the current brand-new master (unless I made a mistake
when uploading). It _would_ lose it without
commit e
Updates:
Labels: Patch-needs_work
Comment #29 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c29
Patchy the autobot says: this loses the second word FAT in
text-spanner-a
Updates:
Labels: Patch-new
Comment #28 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c28
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of th
lilyp...@googlecode.com writes:
> Updates:
> Labels: Patch-needs_work
>
> Comment #25 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
> EventChord around rhythmic events by default.
> http://code.google.com/p/lilypond/issues/detail?id=2070#c25
>
> Patchy the autobot says: based on
Comment #33 on issue 1943 by mts...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Building now...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinf
Comment #4 on issue 2235 by pfr.haer...@gmail.com: \partcombine: accidental
reminders of first part lost
http://code.google.com/p/lilypond/issues/detail?id=2235
I think, that almost ever the extra context is the reason for the
accidental, and therefore would prefer, that it is shown in the
Comment #32 on issue 1943 by gra...@percival-music.ca: lilypond after
2.15.8 fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
it's in the osx-lilypad-universal dir, called -0.6.tar.gz now.
___
bug-lilypond mailing list
bug
Comment #27 on issue 2070 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
staging is vaguely in limbo: I've disabled the crontab on my desktop since
I want to control when it gets bogged dow
Comment #31 on issue 1943 by mts...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Sorry, I had no clue it was that easy.
Could you please post Christian's binary as something like:
http://lilypond.org/download/gub-sources/osx-lily
Comment #26 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
The last upload is based on current master, the current work is based on
staging. Since staging has not been bounced to master
On Thu, Jan 19, 2012 at 06:10:14PM +, Carl Sorensen wrote:
>
> On 1/19/12 10:05 AM, "Graham Percival" wrote:
>
> >The proper thing is to:
> >- make a branch
> >- do a local lsr update
maybe better to push right here?
> >- make your code and doc change
> >- do a local lsr update
>
> Why is
Updates:
Labels: -Patch-review Patch-push
Comment #3 on issue 2237 by gra...@percival-music.ca: Patch: Fix spelling
in input/regression/*.ly
http://code.google.com/p/lilypond/issues/detail?id=2237
(No comment was entered for this change.)
Updates:
Labels: Patch-needs_work
Comment #25 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c25
Patchy the autobot says: based on current master, this removes the pitched
Hello,
Just reported on the French Users mailing list:
Snippet
%% subdivideBeams does not work anymore with 16th tuplets.
%% With 2.15.26 only the second beat is subdivided as expected.
%% Worked well with stable 2.14.2, so this is a Regression.
\version "2.15.26"
\relative c'' {
\set s
Updates:
Labels: Patch-review
Comment #2 on issue 2238 by lilypond...@gmail.com: Patch: Spelling fixes in
comments and documentation
http://code.google.com/p/lilypond/issues/detail?id=2238#c2
Patchy the autobot says: LGTM.
___
bug-lilypond
Comment #30 on issue 1943 by gra...@percival-music.ca: lilypond after
2.15.8 fails on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Mike and Carl,
Are you asking because you tried doing something like the 2-line change
here:
https://github.com/janneke/gub/commit/499f
Updates:
Labels: Patch-review
Comment #2 on issue 2237 by lilypond...@gmail.com: Patch: Fix spelling in
input/regression/*.ly
http://code.google.com/p/lilypond/issues/detail?id=2237#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailin
Comment #29 on issue 1943 by mts...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Thanks Christian.
One issue is that we roll our own Python with LilyPond, so the solution of
downloading the binary from the python website would l
Comment #28 on issue 1943 by chh...@gmail.com: lilypond after 2.15.8 fails
on x86 Macs
http://code.google.com/p/lilypond/issues/detail?id=1943
Building the application bundle requires a Mac OS X machine. For future
reference here are my notes on how i built the current bundle:
http://klar
Updates:
Status: Started
Owner: pkx1...@gmail.com
Labels: -Type-Enhancement Type-Documentation
Comment #1 on issue 2238 by pkx1...@gmail.com: Patch: Spelling fixes in
comments and documentation
http://code.google.com/p/lilypond/issues/detail?id=2238
(No comment was ent
Updates:
Status: Started
Owner: pkx1...@gmail.com
Labels: -Type-Enhancement Type-Documentation
Comment #1 on issue 2237 by pkx1...@gmail.com: Patch: Fix spelling in
input/regression/*.ly
http://code.google.com/p/lilypond/issues/detail?id=2237
(No comment was entered fo
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2238 by pkx1...@gmail.com: Patch: Spelling fixes in comments and
documentation
http://code.google.com/p/lilypond/issues/detail?id=2238
Spelling fixes in comments and documentation
achive -> achieve
defintion -> definition
d
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2237 by pkx1...@gmail.com: Patch: Fix spelling in
input/regression/*.ly
http://code.google.com/p/lilypond/issues/detail?id=2237
Fix spelling in input/regression/*.ly
accomodate -> accommodate
adn -> and
eigth -> eighth
exce
Updates:
Status: Fixed
Labels: -Patch-review Fixed_2_15_27
Comment #2 on issue 2233 by d...@gnu.org: Patch: Make inherited stream
event properties immutable.
http://code.google.com/p/lilypond/issues/detail?id=2233
Pushed to staging as e8f544af29c93145d122efa8dcfc0548d9b84f0b
62 matches
Mail list logo
