On Dec 31, 2011, at 10:56 PM, Jay Anderson wrote:
> I've been unable to create a good small example so far. When I take
> out seemingly unrelated sections it compiles which makes it difficult
> to narrow down. Removing the "Span_bar_stub_engraver" from my
> PianoStaff fixes the segfault, but what
Updates:
Summary: Web: Added 'Ripple' to easier-editing section
Status: Started
Owner: pkx1...@gmail.com
Labels: -Type-Enhancement Type-Documentation
Comment #1 on issue 2163 by pkx1...@gmail.com: Web: Added 'Ripple' to
easier-editing section
http://code.google.
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2163 by pkx1...@gmail.com: Patch: Web: Added 'Ripple' to
easier-editing section
http://code.google.com/p/lilypond/issues/detail?id=2163
Web: Added 'Ripple' to easier-editing section
Also re-ordered existing listings for thi
Updates:
Labels: -Priority-Low
Comment #5 on issue 1325 by pkx1...@gmail.com: Volta bracket going over to
next line
http://code.google.com/p/lilypond/issues/detail?id=1325
Keith, can you suggest some rough text I can make a patch.
James
_
Comment #5 on issue 1566 by pkx1...@gmail.com: Beam properties won't be
changed after the start of the beam
http://code.google.com/p/lilypond/issues/detail?id=1566
Carl, see issue 2162 - I've added an @knownissue (in case this is every
improved) so if you want you can move this back to enha
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2162 by pkx1...@gmail.com: Patch: Doc: NR added @knownissue for
beam properties
http://code.google.com/p/lilypond/issues/detail?id=2162
Doc: NR added @knownissue for beam properties
Used Carl S's wording from comment #3 of
Updates:
Status: Fixed
Labels: -Patch-review
Comment #13 on issue 2136 by pkx1...@gmail.com: Patch: Doc: Usage --include
option layout consistency
http://code.google.com/p/lilypond/issues/detail?id=2136
Pushed as commit
Sat, 31 Dec 2011 23:03:17 + (23:03 +)
commit 96
Updates:
Labels: Patch-new
Comment #6 on issue 2093 by pkx1...@gmail.com: Doc: NR
alternativeNumberingStyle (fix issue 2059) needs to be documented
http://code.google.com/p/lilypond/issues/detail?id=2093#c6
Doc: NR added snippet for Alt Bar Numbering
Tracker item 2093
Added snippet
I've been unable to create a good small example so far. When I take
out seemingly unrelated sections it compiles which makes it difficult
to narrow down. Removing the "Span_bar_stub_engraver" from my
PianoStaff fixes the segfault, but what won't work if I do this?
Below is at least the stack trace
Updates:
Labels: Patch-review
Comment #4 on issue 2153 by lilypond...@gmail.com: piano pedal bracket
should stop at requested moment
http://code.google.com/p/lilypond/issues/detail?id=2153#c4
Patchy the autobot says: LGTM.
___
bug-lilypond
Comment #15 on issue 1964 by gra...@percival-music.ca: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964
since we'll be making a new lilydev anyway, could we get astyle 2.02
exactly? I just have no heart for another round of C++ syntax fighting,
which is what astyle 2.02.1
Comment #3 on issue 2153 by gra...@percival-music.ca: piano pedal bracket
should stop at requested moment
http://code.google.com/p/lilypond/issues/detail?id=2153
http://codereview.appspot.com/5500093
___
bug-lilypond mailing list
bug-lilypond@gnu.
Updates:
Labels: Patch-review
Comment #2 on issue 2158 by lilypond...@gmail.com: Patch: Sketch of not
remaking html files
http://code.google.com/p/lilypond/issues/detail?id=2158#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing li
Updates:
Labels: Patch-review
Comment #1 on issue 2159 by lilypond...@gmail.com: Patch: lexer.ll: Warn
about non-UTF-8 characters
http://code.google.com/p/lilypond/issues/detail?id=2159#c1
Patchy the autobot says: LGTM.
___
bug-lilypond ma
Updates:
Labels: Patch-review
Comment #7 on issue 1802 by lilypond...@gmail.com: system-system-spacing in
lilypond-book-file within a LaTeX file
http://code.google.com/p/lilypond/issues/detail?id=1802#c7
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-review
Comment #12 on issue 2136 by lilypond...@gmail.com: Patch: Doc: Usage
--include option layout consistency
http://code.google.com/p/lilypond/issues/detail?id=2136#c12
Patchy the autobot says: LGTM.
___
bug-lily
Status: Accepted
Owner:
Labels: Type-Maintainability
New issue 2161 by gra...@percival-music.ca: Nonfastforwarding push to
staging
http://code.google.com/p/lilypond/issues/detail?id=2161
There's a suggestion to use something called "git hooks" to help us avoid
making certain mistakes i
Comment #14 on issue 2027 by gra...@percival-music.ca: make website doesn't
have dependencies
http://code.google.com/p/lilypond/issues/detail?id=2027
LILYPOND_WEB_MEDIA_GIT is completely distinct from the dependencies issue;
it's now issue 2160.
__
Status: Accepted
Owner:
Labels: Type-Critical
New issue 2160 by gra...@percival-music.ca: document LILYPOND_WEB_MEDIA_GIT
http://code.google.com/p/lilypond/issues/detail?id=2160
to create the website exactly as it is on lilypond.org, you need a clone of
https://github.com/gperciva/lilypon
Comment #7 on issue 2156 by philehol...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
OK - Fix dependencies for translated manuals is the culprit. If I run make
-d doc and redirect the output, I hit a logfile of 3.8 Gigs after 15
minutes. It's looping. Us
Phil,
On 31/12/11 15:34, lilyp...@googlecode.com wrote:
>
> Comment #12 on issue 1826 by philehol...@gmail.com: Guile 2.0
> compat: `conditional-circle-markup' definition needs to be
> relocated http://code.google.com/p/lilypond/issues/detail?id=1826
>
> How would this fix be verified, please?
On
Comment #6 on issue 2156 by philehol...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
OK - looking at "Unify the rules and variables for xref-map files" I've run
make; make doc and then compared the file-list generated prior to applying
the patch with the on
Comment #20 on issue 1781 by dzhan...@gmail.com: Mac OS X 10.7 (Lion)
cannot run LilyPond
http://code.google.com/p/lilypond/issues/detail?id=1781
@comment 19: Are you saying I could follow one of those routes to use
lilypond?
Or do I wait until a proper release for Lion is available?
___
Updates:
Status: Started
Owner: philehol...@gmail.com
Comment #5 on issue 2156 by philehol...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
First one of these checked with make, make doc and compare of build dir:
all clear, so "Build: Update ti
Updates:
Status: Verified
Comment #4 on issue 2131 by philehol...@gmail.com: Patch: Tie LilyPond,
lexer and parser together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131
(No comment was entered for this change.)
___
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #8 on issue 2122 by philehol...@gmail.com: Regression in
chord-name-exceptions.ly - badly spaced chord names
http://code.google.com/p/lilypond/issues/detail?id=2122
(No comment was entered for this change.)
_
Updates:
Status: Verified
Comment #8 on issue 2105 by philehol...@gmail.com: Patch: Remove warning
and .aux file left over by lilypond-book.
http://code.google.com/p/lilypond/issues/detail?id=2105
Commitish verified
___
bug-lilypond mailin
Updates:
Status: Verified
Comment #12 on issue 2103 by philehol...@gmail.com: Patch: Output a newline
by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
Commit verified
___
bug-lilypond mail
Updates:
Labels: Fixed_2_15_24
Comment #8 on issue 2090 by philehol...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
(No comment was entered for this change.)
___
b
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #10 on issue 2084 by philehol...@gmail.com: script-accidental
avoidance fails for articulations
http://code.google.com/p/lilypond/issues/detail?id=2084
(No comment was entered for this change.)
__
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87ipkwu66v@fencepost.gnu.org...
>> lilyp...@googlecode.com writes:
>>
>>> Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
>>> http://code.google.com/p/lilypond/issues/detail?id=2156
>>>
>>> Phil,
>>>
>>> I *think* yo
Updates:
Labels: -Patch-needs_work Fixed_2_15_24
Comment #19 on issue 2059 by philehol...@gmail.com: Bar numbering of
alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
(No comment was entered for this change.)
___
bug-li
"David Kastrup" wrote in message
news:87ipkwu66v@fencepost.gnu.org...
lilyp...@googlecode.com writes:
Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
Phil,
I *think* you can simply (simply :) ) checkout the broken tree,
Comment #13 on issue 2027 by philehol...@gmail.com: make website doesn't
have dependencies
http://code.google.com/p/lilypond/issues/detail?id=2027
Well - if I now run make website, I get "Need a LILYPOND_WEB_MEDIA_GIT
environment variable!" which may be true but isn't very helpful. I guess
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2159 by d...@gnu.org: Patch: lexer.ll: Warn about non-UTF-8
characters
http://code.google.com/p/lilypond/issues/detail?id=2159
lexer.ll: Warn about non-UTF-8 characters
Making the warnings point to the exact bad byte rather
Updates:
Status: Accepted
Comment #6 on issue 2137 by philehol...@gmail.com: Patch: Doc: NR
improve 'visibility' of 'q' operation
http://code.google.com/p/lilypond/issues/detail?id=2137
(No comment was entered for this change.)
___
bug-lil
Werner LEMBERG writes:
>>> But string handling is delegated to Pango...
>>
>> Not as far as I can see. String _typesetting_ is delegated to Pango.
>
> Ok. My knowledge of the code is too restricted. Does LilyPond itself
> check the validity of UTF-8 somewhere? Otherwise, we could reuse code
Updates:
Status: Accepted
Comment #15 on issue 2149 by philehol...@gmail.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
(No comment was entered for this change.)
___
bug-lilypon
Updates:
Status: Accepted
Comment #1 on issue 2158 by philehol...@gmail.com: Patch: Sketch of not
remaking html files
http://code.google.com/p/lilypond/issues/detail?id=2158
Associated with Issue 2028.
___
bug-lilypond mailing list
bug-lil
Status: New
Owner:
Labels: Type-Patch Patch-new
New issue 2158 by philehol...@gmail.com: Patch: Sketch of not remaking html
files
http://code.google.com/p/lilypond/issues/detail?id=2158
Sketch of not remaking html files
http://codereview.appspot.com/5498093
___
Updates:
Status: Verified
Comment #6 on issue 2020 by philehol...@gmail.com: Patch: avoid cryptic
StopIteration failure from make when 'make check' is run before 'make
test-baseline'
http://code.google.com/p/lilypond/issues/detail?id=2020
Commit verified
__
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #6 on issue 1947 by philehol...@gmail.com: Stem Tremoli for
double-stemmed notes are too short on the right side.
http://code.google.com/p/lilypond/issues/detail?id=1947
(No comment was entered for this change.)
Updates:
Status: Verified
Comment #8 on issue 1927 by philehol...@gmail.com: 2.15.2 doesn't build
anymore on Mageia
http://code.google.com/p/lilypond/issues/detail?id=1927
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #7 on issue 1861 by philehol...@gmail.com: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861
(No comment was entered for this change.)
_
Updates:
Status: Verified
Comment #11 on issue 1835 by philehol...@gmail.com: no learing manual pdf
in dutch
http://code.google.com/p/lilypond/issues/detail?id=1835
http://lilypond.org/doc/v2.15/Documentation/learning/index.nl.html LGTM
__
Comment #12 on issue 1826 by philehol...@gmail.com: Guile 2.0 compat:
`conditional-circle-markup' definition needs to be relocated
http://code.google.com/p/lilypond/issues/detail?id=1826
How would this fix be verified, please?
___
bug-lilypond mai
Updates:
Status: Verified
Comment #19 on issue 1732 by philehol...@gmail.com: occasional segfault
when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Confirming no recent reports of this as a problem.
__
Updates:
Status: Verified
Comment #18 on issue 1377 by philehol...@gmail.com: Enhancement: make the
last-page spacing more consistent and less tight
http://code.google.com/p/lilypond/issues/detail?id=1377
Nice.
___
bug-lilypond mailing lis
Updates:
Labels: Fixed_2_15_24
Comment #3 on issue 1361 by philehol...@gmail.com: Collision: TupletNumber
and Script
http://code.google.com/p/lilypond/issues/detail?id=1361
(No comment was entered for this change.)
___
bug-lilypond mailing
Hello,
On 31 December 2011 15:11, David Kastrup wrote:
> lilyp...@googlecode.com writes:
>
>> Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
>> http://code.google.com/p/lilypond/issues/detail?id=2156
>>
>> Phil,
>>
>> I *think* you can simply (simply :) ) checkout the broken tree, th
Updates:
Status: Verified
Comment #10 on issue 1267 by philehol...@gmail.com: Documentation
for 'ignore-collision is unclear
http://code.google.com/p/lilypond/issues/detail?id=1267
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #14 on issue 1216 by philehol...@gmail.com: DynamicTextSpanners
should end like hairpins
http://code.google.com/p/lilypond/issues/detail?id=1216
(No comment was entered for this change.)
___
bug-lilypond m
lilyp...@googlecode.com writes:
> Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
> http://code.google.com/p/lilypond/issues/detail?id=2156
>
> Phil,
>
> I *think* you can simply (simply :) ) checkout the broken tree, then
> use gitk (as it is easier) to find commit, then reset the hea
Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
Phil,
I *think* you can simply (simply :) ) checkout the broken tree, then use
gitk (as it is easier) to find commit, then reset the head back to there
and then use
git form
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #14 on issue 695 by philehol...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
(No comment was entered for this change.)
___
bug-
Comment #3 on issue 2156 by philehol...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
I'd be happy to grab these as patches, apply them, test each with a full
make/make doc and check the results and then push to staging if they're
OK. Is there an easy way t
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2157 by philehol...@gmail.com: Add "quick URL box" to
documentation
http://code.google.com/p/lilypond/issues/detail?id=2157
It's a pain in the current docs to document URLs and file locations whilst
ensuring that they neither
Updates:
Labels: Patch-new
Comment #6 on issue 1802 by pkx1...@gmail.com: system-system-spacing in
lilypond-book-file within a LaTeX file
http://code.google.com/p/lilypond/issues/detail?id=1802#c6
Doc: Usage added @knownissue for LaTeX
This is for Tracker issue 1802.
Describes that
Hello,
On 31 December 2011 13:47, Chris Morgan wrote:
>> I'm not top posting.
>
> \version "2.15.23" % also 2.14.2
>
> \markup { Here is how beamed quaver tuplets look now; ugly, with some
> colliding
> with the staff lines: }
There are a lot of tracker items this could be
http://code.google.c
> I'm not top posting.
\version "2.15.23" % also 2.14.2
\markup { Here is how beamed quaver tuplets look now; ugly, with some colliding
with the staff lines: }
\relative f' {
\times 2/3 { f8 f f }
\times 2/3 { e e e }
\times 2/3 { d d d }
\times 2/3 { c c c } % All lower notes are the sam
Updates:
Labels: -Patch-new
Comment #4 on issue 2135 by pkx1...@gmail.com: --include option description
not consistent with others in Application Usage
http://code.google.com/p/lilypond/issues/detail?id=2135
(No comment was entered for this change.)
_
Updates:
Labels: -Patch-needs_work Patch-new
Comment #11 on issue 2136 by pkx1...@gmail.com: Patch: Doc: Usage --include
option layout consistency
http://code.google.com/p/lilypond/issues/detail?id=2136
New patch uploaded
http://codereview.appspot.com/5504084/
James
__
Comment #3 on issue 2135 by pkx1...@gmail.com: --include option description
not consistent with others in Application Usage
http://code.google.com/p/lilypond/issues/detail?id=2135#c3
Doc: Usage --include option layout consistency
Tracker 2135
Made description of arguments consistent with ot
Updates:
Labels: -Patch-push Fixed_2_15_24
Comment #9 on issue 257 by philehol...@gmail.com: collision accent and
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=257
(No comment was entered for this change.)
___
bug-lilyp
Comment #19 on issue 1781 by harmathdenes: Mac OS X 10.7 (Lion) cannot run
LilyPond
http://code.google.com/p/lilypond/issues/detail?id=1781
There are several options if you want to use a GUI until a proper fix is
released:
- use the 2.15 development branch
- use one of the advanced editors
Updates:
Labels: Type-Other
Comment #1 on issue 2140 by philehol...@gmail.com: warning issued when
--default-defining an option that lilypond doesn't know
http://code.google.com/p/lilypond/issues/detail?id=2140
(No comment was entered for this change.)
__
lilyp...@googlecode.com writes:
> Comment #2 on issue 2156 by k-ohara5...@oco.net: lost commits
> http://code.google.com/p/lilypond/issues/detail?id=2156
>
> There are only three commits, from Julian, that have not been ported
> over to master :
>
> 3c7c453 Build: Update timestamp when linking fil
Updates:
Labels: Type-Defect
Comment #1 on issue 2151 by philehol...@gmail.com: add-grace-note usage
interferes with MIDI output in same score block
http://code.google.com/p/lilypond/issues/detail?id=2151
(No comment was entered for this change.)
Comment #2 on issue 2156 by k-ohara5...@oco.net: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
There are only three commits, from Julian, that have not been ported over
to master :
3c7c453 Build: Update timestamp when linking files.
01d0af4 Build: Unify the rules and v
Comment #1 on issue 2156 by pkx1...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
Hello,
I'm not sure about the 'approximately 10 commits' calculation - but of
course I am probably wrong - I downloaded staging-broken-dec-23, checked it
out, ran git log --pr
70 matches
Mail list logo
