G.S. Williams writes:
> Hi,
>
> I've been tied up with classical music for several decades,
> and we have always referred to
> pairs of notes as "DUPLETS",
> not,"TUPLETS:.why do you people in the U.S.A. always
> change terminology?
That's not a change. A duplet is a pair of notes against
Status: Accepted
Owner:
Labels: Type-Defect Performance
New issue 2264 by k-ohara5...@oco.net: Line breaking can be slow with very
wide paper
http://code.google.com/p/lilypond/issues/detail?id=2264
Lilypond takes 5 seconds to set this if there are 200 notes, 35 seconds if
there are 400
Hi,
I've been tied up with classical music for several decades,
and we have always referred to
pairs of notes as "DUPLETS",
not,"TUPLETS:.why do you people in the U.S.A. always
change terminology?
I''m curious!
Ciao.
G.S.Williams
___
bug-lily
Updates:
Labels: -Patch-countdown Patch-push
Comment #8 on issue 2256 by colinpkc...@gmail.com: empty strings: tabStaff
insists on stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256
Counted down to 20120129, please push
Updates:
Status: Fixed
Labels: -Patch-needs_work Fixed_2_15_28
Comment #13 on issue 2229 by d...@gnu.org: Patch: Broadcast articulations
not in EventChord
http://code.google.com/p/lilypond/issues/detail?id=2229
This has been committed as part of the 2070 work as
24b50a014e90
Updates:
Status: Fixed
Comment #5 on issue 2247 by d...@gnu.org: Patch: parser.yy: strip
music-wrapper-music inside of EventChord
http://code.google.com/p/lilypond/issues/detail?id=2247
(No comment was entered for this change.)
___
bug-lil
Updates:
Labels: -Patch-review Fixed_2_15_18
Comment #4 on issue 2247 by d...@gnu.org: Patch: parser.yy: strip
music-wrapper-music inside of EventChord
http://code.google.com/p/lilypond/issues/detail?id=2247
True stripping in the parser pushed as
68fdcfe453ddcc300db7e57599e66ff49c9c
Comment #7 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263#c7
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in the lexer/parser.
Instead establish it at
Comment #1 on issue 2261 by k-ohara5...@oco.net: Sustain off placement bug
http://code.google.com/p/lilypond/issues/detail?id=2261
The modern pedal indication styles, \set Staff.pedalSustainStyle = #'mixed
fit properly close to the staff.
We might fix both this and issue 727 by treating the old
Graham Percival writes:
> On Sun, Jan 29, 2012 at 06:34:16PM +0100, David Kastrup wrote:
>> lilyp...@googlecode.com writes:
>>
>> > Amusingly, apparently somebody added code to handle the < > bits, but
>> > not the URL: part.
>>
>> Both forms are in use, but I thought the URL: form was, stupid
On Sun, Jan 29, 2012 at 06:34:16PM +0100, David Kastrup wrote:
> lilyp...@googlecode.com writes:
>
> > Amusingly, apparently somebody added code to handle the < > bits, but
> > not the URL: part.
>
> Both forms are in use, but I thought the URL: form was, stupid as it
> looks, more or less consid
lilyp...@googlecode.com writes:
> Comment #6 on issue 2263 by gra...@percival-music.ca: Reimplement
> chord repetition
> http://code.google.com/p/lilypond/issues/detail?id=2263
>
> your url field began with a . This code does
> not parse urls in that format:
> https://github.com/gperciva/lilypond
lilyp...@googlecode.com writes:
> Comment #5 on issue 2263 by gra...@percival-music.ca: Reimplement
> chord repetition
> http://code.google.com/p/lilypond/issues/detail?id=2263
>
> Apparently the test source tree is missing
> 2c5b82a7c0e500623e0e0cdcadd3b0a2703825a3
> which would explain the fai
Comment #6 on issue 2263 by gra...@percival-music.ca: Reimplement chord
repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
your url field began with a . This code does not
parse urls in that format:
https://github.com/gperciva/lilypond-extra/blob/master/patches/projecthost
Comment #5 on issue 2263 by gra...@percival-music.ca: Reimplement chord
repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Apparently the test source tree is missing
2c5b82a7c0e500623e0e0cdcadd3b0a2703825a3
which would explain the failure to apply the patch.
Git people, exp
Comment #4 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Not likely. Patchy has refused even starting on issue 1110. It is now
happily engaged with 2263. It is possible that this may be because the
Rietveld issue change
Comment #3 on issue 2263 by gra...@percival-music.ca: Reimplement chord
repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Julien fixed the "too many comments" problem.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lis
Updates:
Status: Started
Labels: Patch-new
Comment #2 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
(No comment was entered for this change.)
___
bug-lilypond maili
Updates:
Status: Duplicate
Labels: -Patch-new
Mergedinto: 2263
Comment #48 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
Likely blocked because of Patchy API probl
Comment #1 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Issue 1110 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailma
Status: Accepted
Owner: d...@gnu.org
New issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Since Patchy spews out totally useless
Trying issue 1110
Something went wrong; omitting patch for issue 1110
No new patches to test
reports,
Updates:
Labels: -Patch-needs_work Patch-new
Comment #47 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
Since master has now finally bumped to staging, the diff in the mentioned
> Patchy the autobot says: patch failed:
> scm/define-music-display-methods.scm:42
:-) The answer to life, the universe and everything.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #46 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
Then either your patchy is not working with the current master, or it is
not testing the current Rietveld review (I don't know
Comment #10 on issue 2209 by philehol...@gmail.com: lilypond-book creates
uncompilable latex files (windows)
http://code.google.com/p/lilypond/issues/detail?id=2209
Needs someone with pdflatex installed on Windows to verify...
___
bug-lilypond mai
Comment #45 on issue 1110 by gra...@percival-music.ca: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
oops, copy&paste error. That should be line 428.
___
bug-lilypond mail
Updates:
Labels: Patch-needs_work
Comment #44 on issue 1110 by lilypond...@gmail.com: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c44
Patchy the autobot says: patch failed:
scm/define-music-display-methods.
Updates:
Status: Verified
Comment #10 on issue 2210 by philehol...@gmail.com: Patch: Build: Top-level
GNUmakefile
http://code.google.com/p/lilypond/issues/detail?id=2210
Verified GNUmakefile in /build is read-only
___
bug-lilypond mailing
Comment #43 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#c43
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in t
Updates:
Labels: Patch-review
Comment #4 on issue 2255 by lilypond...@gmail.com: Doc: NR Add @warning for
Margin adjustment'
http://code.google.com/p/lilypond/issues/detail?id=2255#c4
Patchy the autobot says: LGTM.
___
bug-lilypond mailing
Updates:
Labels: Patch-review
Comment #17 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#c17
Patchy the autobot says: LGTM.
___
bug-lilypon
Updates:
Labels: Patch-review
Comment #3 on issue 2179 by lilypond...@gmail.com: Improve warnings about
spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\
{...} >> constructs
http://code.google.com/p/lilypond/issues/detail?id=2179#c3
Patchy the autobot says: L
Updates:
Labels: Patch-review
Comment #8 on issue 2162 by lilypond...@gmail.com: Patch: Doc: NR added
@knownissue for beam properties
http://code.google.com/p/lilypond/issues/detail?id=2162#c8
Patchy the autobot says: LGTM.
___
bug-lilypon
Updates:
Labels: Patch-review
Comment #6 on issue 2040 by lilypond...@gmail.com: Documentation for
unpure-pure-containers
http://code.google.com/p/lilypond/issues/detail?id=2040#c6
Patchy the autobot says: LGTM.
___
bug-lilypond mailing li
Got no answers on -devel, so I forward here (probably more appropriate
place).
Thanks,
Federico
Il 05/01/2012 13:44, Federico Bruni ha scritto:
Issue 1721 reported that @rlsr{Name} keeps the text in english but
translates the link in the translated manuals (no idea where the
translation comes
Hi,
On Sun, Jan 29, 2012 at 10:51:36AM -, Phil Holmes wrote:
> I know Brett is no longer squadding, and that Marek and James have
> been taking up the slack. Could I have a roll-call of who is doing
> which day, so I can update the CG please?
I'd like to resume doing Thursday. Apologies for
Comment #5 on issue 2251 by gra...@percival-music.ca: website still doesn't
auto-update
http://code.google.com/p/lilypond/issues/detail?id=2251
more info:
yeah, it's definitely missing all the $LILYPOND_WEB_MEDIA_GIT stuff, which
means that the currently-printed instructions are at least 8
lilyp...@googlecode.com writes:
> Updates:
> Labels: -Type-Defect Type-Critical
>
> Comment #7 on issue 2256 by gra...@percival-music.ca: empty strings:
> tabStaff insists on stringnumbers and looses notes
> http://code.google.com/p/lilypond/issues/detail?id=2256
>
> according to the CG, any
Updates:
Labels: -Type-Ugly Type-Critical
Comment #7 on issue 2260 by gra...@percival-music.ca: line-broken spanners
start too far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
according to the CG, any regression since the last TWO stable
Updates:
Labels: -Type-Defect Type-Critical
Comment #7 on issue 2256 by gra...@percival-music.ca: empty strings:
tabStaff insists on stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256
according to the CG, any regression since the last TWO stable rel
Comment #4 on issue 2251 by gra...@percival-music.ca: website still doesn't
auto-update
http://code.google.com/p/lilypond/issues/detail?id=2251
http://lilypond.org/doc/v2.15/Documentation/contributor/uploading-and-security
HOWEVER, note:
- that page might contain obsolete information
- the
Updates:
Status: Started
Labels: -Patch-push
Comment #7 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
pushed as 5c6fbbdb2cc02f7675cc4233a890914cc93cf793
The benefits won'
Updates:
Labels: -Patch-push Patch-needs_work
Comment #13 on issue 2223 by julien.r...@gmail.com: Regtest for
lilypond-book are not running
http://code.google.com/p/lilypond/issues/detail?id=2223
It looks like running multiple lilypond-book instances in parallel is
causing problems
Comment #3 on issue 2251 by julien.r...@gmail.com: website still doesn't
auto-update
http://code.google.com/p/lilypond/issues/detail?id=2251
What is this make-website.sh script?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.
Comment #2 on issue 2251 by gra...@percival-music.ca: website still doesn't
auto-update
http://code.google.com/p/lilypond/issues/detail?id=2251
it's type-critical because I absolutely refuse to manually ssh into
lilypond.org to announce a stable release.
_
Comment #1 on issue 2251 by d...@gnu.org: website still doesn't auto-update
http://code.google.com/p/lilypond/issues/detail?id=2251
Since this does not concern functionality accessible by the user from an
installed version of LilyPond, I would lean to remove "Type-Critical"
here. It does no
Updates:
Labels: -Type-Critical Type-Ugly
Comment #6 on issue 2260 by d...@gnu.org: line-broken spanners start too
far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Downgraded to "Ugly" since the regression occured before the last stable
Updates:
Labels: -Type-Critical Type-Defect
Comment #6 on issue 2256 by d...@gnu.org: empty strings: tabStaff insists
on stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256
Changing type to "Defect" instead of "Critical" since it is not a
regressio
Comment #42 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#c42
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in t
Updates:
Status: Verified
Comment #10 on issue by philehol...@gmail.com: lilypond-book fails
with html input
http://code.google.com/p/lilypond/issues/detail?id=
(No comment was entered for this change.)
___
bug-lilypond mailing li
Updates:
Status: Verified
Comment #11 on issue 2231 by philehol...@gmail.com: Tuplet bracket makes
space for dynamic but dynamic is placed underneath bracket
http://code.google.com/p/lilypond/issues/detail?id=2231
(No comment was entered for this change.)
___
On Sun, Jan 29, 2012 at 11:00:03AM +, James wrote:
> Here Mr Holmes!
>
> On 29 January 2012 10:51, Phil Holmes wrote:
> > I know Brett is no longer squadding, and that Marek and James have been
> > taking up the slack. Could I have a roll-call of who is doing which day, so
> > I can update t
Updates:
Status: Verified
Comment #4 on issue 2160 by philehol...@gmail.com: document
LILYPOND_WEB_MEDIA_GIT
http://code.google.com/p/lilypond/issues/detail?id=2160
(No comment was entered for this change.)
___
bug-lilypond mailing list
bu
Updates:
Status: Verified
Comment #28 on issue 2100 by philehol...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100
(No comment was entered for this change.)
___
bug-li
Updates:
Status: Verified
Comment #37 on issue 1997 by gra...@percival-music.ca: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
since we can compile GUB, this must be fixed.
___
bug-lilypond
Comment #36 on issue 1997 by philehol...@gmail.com: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
Needs someone with the correct development environment to verify.
___
bug-lilypond mailing list
bug-
Updates:
Status: Verified
Comment #43 on issue 1933 by philehol...@gmail.com: Lilypond-book
subprocess doesn't work on mingw
http://code.google.com/p/lilypond/issues/detail?id=1933
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #23 on issue 1846 by philehol...@gmail.com: Improves horizontal
spacing of axis groups that SpanBar grobs traverse
http://code.google.com/p/lilypond/issues/detail?id=1846
Verified from committish
___
bug-l
Updates:
Status: Verified
Comment #14 on issue 1802 by philehol...@gmail.com: system-system-spacing
in lilypond-book-file within a LaTeX file
http://code.google.com/p/lilypond/issues/detail?id=1802
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #21 on issue 1781 by philehol...@gmail.com: Mac OS X 10.7 (Lion)
cannot run LilyPond
http://code.google.com/p/lilypond/issues/detail?id=1781
Verified based on Comment 13
___
bug-lilypond mailing list
bug-l
Updates:
Labels: -Patch-needs_work Patch-new
Comment #7 on 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
Updates:
Owner: ---
Labels: -Patch-new Patch-needs_work
Comment #8 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
I think now this issue has been split off into 2 differen
Updates:
Status: Verified
Labels: -Needs-evidence
Comment #4 on issue 1352 by philehol...@gmail.com: Polyphonic dots
placement is inconsistent, confusing and prone to collisions
http://code.google.com/p/lilypond/issues/detail?id=1352
(No comment was entered for this change.)
Updates:
Status: Verified
Comment #3 on issue 1230 by philehol...@gmail.com: Dot may collide with
flag with some stem's 'length values
http://code.google.com/p/lilypond/issues/detail?id=1230
(No comment was entered for this change.)
___
bu
Updates:
Status: Verified
Comment #3 on issue 1183 by philehol...@gmail.com: @rcontrib{} from topdocs
doesn't work
http://code.google.com/p/lilypond/issues/detail?id=1183
(No comment was entered for this change.)
___
bug-lilypond mailing l
Updates:
Labels: Patch-new
Comment #7 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#c7
Doc: NR added @knownissue for beam properties
Used Carl S's wording from comment #3 of Tra
Updates:
Status: Verified
Comment #7 on issue 1091 by philehol...@gmail.com: Dot in \voiceOne
collides with stem in \voiceThree in short intervals
http://code.google.com/p/lilypond/issues/detail?id=1091
Verified using code from initial report. Nice job.
Updates:
Labels: Patch-new
Comment #16 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#c16
Doc: NR Section on Upbeats made clearer
Tracker issue 2189
Created simpler and clearer @lilypond
Hello
2012/1/29 Phil Holmes
> I know Brett is no longer squadding, and that Marek and James have been
> taking up the slack. Could I have a roll-call of who is doing which day,
> so I can update the CG please?
>
I am doing Wednesday and Friday.
Marek
___
Updates:
Labels: Patch-new
Comment #5 on issue 2040 by pkx1...@gmail.com: Documentation for
unpure-pure-containers
http://code.google.com/p/lilypond/issues/detail?id=2040#c5
Doc: NR 5.5.5 Adv tweaks - Unpure-pure containers
Tracker issue 2040
Added information about Unpure-pure cont
Updates:
Labels: Patch-new
Comment #3 on issue 2255 by pkx1...@gmail.com: Doc: NR Add @warning for
Margin adjustment'
http://code.google.com/p/lilypond/issues/detail?id=2255#c3
Doc: NR @knownissues for margins w/paper-size
Tracker issue 2255
Explain that using explicit paper-sizes w
Updates:
Labels: Patch-new
Comment #2 on issue 2179 by pkx1...@gmail.com: Improve warnings about
spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\
{...} >> constructs
http://code.google.com/p/lilypond/issues/detail?id=2179#c2
Doc: NR/LM @warning for multi voi
Updates:
Status: Verified
Comment #3 on issue 856 by philehol...@gmail.com: links in Snippets appear
to not work for snippets in multiple categories
http://code.google.com/p/lilypond/issues/detail?id=856
(No comment was entered for this change.)
_
Here Mr Holmes!
On 29 January 2012 10:51, Phil Holmes wrote:
> I know Brett is no longer squadding, and that Marek and James have been
> taking up the slack. Could I have a roll-call of who is doing which day, so
> I can update the CG please?
I offered to do Saturdays.
--
--
James
_
Updates:
Status: Verified
Labels: -Patch-needs_work
Comment #12 on issue 737 by philehol...@gmail.com: Enhancement: support for
footnotes and/or endnotes.
http://code.google.com/p/lilypond/issues/detail?id=737
Verified from
http://lilypond.org/doc/v2.15/Documentation/notatio
I know Brett is no longer squadding, and that Marek and James have been
taking up the slack. Could I have a roll-call of who is doing which day, so
I can update the CG please?
--
Phil Holmes
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Comment #2 on issue 2178 by pkx1...@gmail.com: NR: clarify the
subsection "Automatic accidentals" of section 1.1.3
http://code.google.com/p/lilypond/issues/detail?id=2178
Ole,
You are going to have give more specifics here. What exactly does 'scope'
mean in this context and perhaps a simpl
Updates:
Status: Started
Owner: pkx1...@gmail.com
Comment #1 on issue 2179 by pkx1...@gmail.com: Improve warnings about
spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\
{...} >> constructs
http://code.google.com/p/lilypond/issues/detail?id=2179
(No c
Updates:
Status: Invalid
Comment #1 on issue 2262 by mts...@gmail.com: Patch: Creates a MIDI note
length formatter
http://code.google.com/p/lilypond/issues/detail?id=2262
(No comment was entered for this change.)
___
bug-lilypond mailing l
Updates:
Status: Started
Owner: pkx1...@gmail.com
Comment #2 on issue 2255 by pkx1...@gmail.com: Doc: NR Add @warning for
Margin adjustment'
http://code.google.com/p/lilypond/issues/detail?id=2255
(No comment was entered for this change.)
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2262 by mts...@gmail.com: Patch: Creates a MIDI note length
formatter
http://code.google.com/p/lilypond/issues/detail?id=2262
Creates a MIDI note length formatter
http://codereview.appspot.com/5576062
Comment #3 on issue 1717 by berger.j...@gmail.com: Possible incompatibility
with Ghostscript 9 (was: Full notes and half notes are drawn filled)
http://code.google.com/p/lilypond/issues/detail?id=1717
It works now with lilypond 2.14.2-4.
___
bug-l
82 matches
Mail list logo
