Comment #13 on issue 2203 by lemzw...@gmail.com: Patch: separate narrowed
accidentals
http://code.google.com/p/lilypond/issues/detail?id=2203
David,
is your remark of general nature? Otherwise, could be more specific,
please? For me, Janek's first try is fine, and later on he might
Updates:
Status: Verified
Comment #12 on issue 2090 by elu...@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.)
___
Comment #14 on issue 2203 by pkx1...@gmail.com: Patch: separate narrowed
accidentals
http://code.google.com/p/lilypond/issues/detail?id=2203
Why are we including 'Accidentals' in with 'KeySignature' - yes we use
sharps and flats in both but they are distinct musical 'things' and the
In http://lists.gnu.org/archive/html/bug-lilypond/2011-04/msg00148.html
Phil Holmes wrote:
to my eye it looks OK.
If there is still a problem, could you be explicit about what it is?
See http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00183.html
To make the problem _visible_,
Updates:
Labels: Patch-new
Comment #3 on issue 2206 by d...@gnu.org: Patch: Let \footnote do the job
of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob
http://code.google.com/p/lilypond/issues/detail?id=2206#c3
Let \footnote do the job of \footnote, \footnoteGrob,
2012/1/9 Aurélien Bello wrote to bug-lilypond@gnu.org:
I would like to Inform you about a production:
Last summer I re-orchestrated the Pictures at an exhibition
of Mussorgsky and made the whole orchestra material and
the score using LilyPond. [...]
2012/1/10 Xavier Scheuer
Comment #5 on issue 1788 by d...@gnu.org: auto numbering footnote checkin
doesn't play with \null and \musicglyph
http://code.google.com/p/lilypond/issues/detail?id=1788
What's the status of this problem report? It appears to me that it has
been overtaken by the development mostly, even
Status: Accepted
Owner: pkx1...@gmail.com
Labels: Type-Documentation
New issue 2213 by pkx1...@gmail.com: Update documentation for \footnotes in
Notation Reference
http://code.google.com/p/lilypond/issues/detail?id=2213
From
http://codereview.appspot.com/5527058/
--snip--
On 2012/01/11
Comment #8 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
b70e6aaf640755d503add64bec847126761bc8c0 was broken and thus deleted.
Pushed now as 67f64c0bdf4cd469de73b135df5ba61cbfea15f7
hi
compiling a ly file with obviously wrong version number yields
GNU LilyPond 2.15.24
Processing `test2.ly'
Parsing...
error: program too old: 2.15.24 (file requires: 2.15.26)
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1
Comment #35 on issue 1948 by elu...@gmail.com: Windows install clobbered
system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
I also downloaded and installed: no change to the path.
should the status be changed - verified?
___
Comment #15 on issue 2203 by n.putt...@gmail.com: Patch: separate narrowed
accidentals
http://code.google.com/p/lilypond/issues/detail?id=2203
Janek, you must add accurate boxes for the new accidentals before pushing
this, otherwise the natural and flat will get poor positioning in sixths.
Comment #16 on issue 1964 by janek.li...@gmail.com: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964
James,
i've found a small problem: the link to CG which is placed on desktop
points to CG from 2.13 series, not current CG.
Comment #5 on issue 2209 by julien.r...@gmail.com: lilypond-book creates
uncompilable latex files (windows)
http://code.google.com/p/lilypond/issues/detail?id=2209
I did not face Issue 1933. One or a combination of the following could
explain it:
1. lilypond-book is run on a .lytex file,
Updates:
Labels: Needs-evidence
Comment #2 on issue 1907 by janek.li...@gmail.com: accidentals in
chordNames have diffferent vertical alignment depending on language
http://code.google.com/p/lilypond/issues/detail?id=1907
(No comment was entered for this change.)
Comment #19 on issue 2193 by n.putt...@gmail.com: collision between beams
and flags
http://code.google.com/p/lilypond/issues/detail?id=2193
Surely the 2.14 output is bad too? It makes the rest look as if it's part
of the lower voice, encompassed by the beam.
I think the rest should be
Comment #15 on issue 2171 by d...@gnu.org: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
What is so special about DOM-id's that would warrant code hand-tailored to
them and nothing else? I am pretty confident that this is fringe
Updates:
Labels: Patch-new
Comment #8 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't
rebuild everything each time unless necessary.
http://code.google.com/p/lilypond/issues/detail?id=2125#c8
Build: Don't rebuild everything each time unless necessary.
- Unify the rules
Updates:
Status: Started
Comment #9 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't
rebuild everything each time unless necessary.
http://code.google.com/p/lilypond/issues/detail?id=2125
(No comment was entered for this change.)
Comment #16 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 mind calling it `id' plain and simple. The docstring could then
say that, depending on the backend, this will put the grob in a
Updates:
Blockedon: 2206
Comment #1 on issue 2213 by d...@gnu.org: Update documentation for
\footnotes in Notation Reference
http://code.google.com/p/lilypond/issues/detail?id=2213
I think that the best bet for getting this done speedily is to first have
issue 2206 go through the
Issue 2206: Patch: Let \footnote do the job of \footnote, \footnoteGrob,
\autoFootnote and \autoFootnoteGrob
http://code.google.com/p/lilypond/issues/detail?id=2206
This issue is now blocking issue 2213.
See http://code.google.com/p/lilypond/issues/detail?id=2213
--
You received this message
Updates:
Status: Fixed
Owner: gra...@percival-music.ca
Comment #6 on issue 857 by julien.r...@gmail.com: translations status
html-texinfo
http://code.google.com/p/lilypond/issues/detail?id=857
Looks fixed to me
___
bug-lilypond
Updates:
Status: Fixed
Labels: Fixed_2_15_24
Comment #2 on issue 1597 by julien.r...@gmail.com: Windows install can
cause PATH to overflow
http://code.google.com/p/lilypond/issues/detail?id=1597
Fixed by the fix to Issue 1948
___
Updates:
Status: Fixed
Comment #20 on issue 2193 by mts...@gmail.com: collision between beams and
flags
http://code.google.com/p/lilypond/issues/detail?id=2193
Pushed as c2734a1ff448b3af37a819db8d00b0a14fff00e9.
___
bug-lilypond mailing
Comment #5 on issue 2180 by mts...@gmail.com: beams are detached from stems
http://code.google.com/p/lilypond/issues/detail?id=2180
Sorry - I'm slammed w/ work for the next week-ish.
I'm sure I can fix it, but I won't be getting around to it until a bit.
Sorry!
Comment #36 on issue 1948 by philehol...@gmail.com: Windows install
clobbered system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
Yes. We have a principle that the person marking it as fixed can't mark as
verified, so I can't but you can.
Updates:
Status: Verified
Comment #37 on issue 1948 by elu...@gmail.com: Windows install clobbered
system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
done
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Updates:
Status: Verified
Comment #3 on issue 1597 by elu...@gmail.com: Windows install can cause
PATH to overflow
http://code.google.com/p/lilypond/issues/detail?id=1597
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Status: Verified
Comment #15 on issue 695 by elu...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
all 3 examples above look good now
___
bug-lilypond mailing list
Comment #8 on issue 1861 by elu...@gmail.com: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861
the dynamics in the Dynamics context look fine - but combined with the
former dynamics directly attached to the notes I get the
Comment #6 on issue 2180 by m...@apollinemike.com: beams are detached from
stems
http://code.google.com/p/lilypond/issues/detail?id=2180
Can't write music anymore...thoughts too clear...LilyPond development makes
brain mushier, thus more conducive to composition...
Spending 10 minutes
Hi all I'm running make doc-stage-1 after
$ cd build
$ git checkout master
$ ../configure --disable-optimising
$ make
$ make test-baseline
$ git checkout T2026-1
$ make test-clean
$ make check
$ make doc-clean
Make doc-clean fails with:
.
.
.
Try replacing the current LSR377 demo code as in the attachment.
This file (visible.ly) includes a linebreak+leftBracket combination,
and thus exercises the custos trick.
When the break alignment override is corrected the bracket at the
start of the second line moves to the right of the key
On 11 January 2012 21:03, Robin Bannister r...@dataway.ch wrote:
It is still incorrect despite the update reported today on lilypond-user.
http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00196.html
It's correct now.
Cheers,
Neil
___
On 11/01/2012 3:58 PM, Ian Hulin wrote:
Hi all I'm running make doc-stage-1 after
$ cd build
$ git checkout master
$ ../configure --disable-optimising
$ make
$ make test-baseline
$ git checkout T2026-1
$ make test-clean
$ make check
$ make doc-clean
Make doc-clean fails with:
.
.
.
Hi Julien,
On 11/01/12 21:48, Julien Rioux wrote:
On 11/01/2012 3:58 PM, Ian Hulin wrote:
Hi all I'm running make doc-stage-1 after
$ cd build $ git checkout master $ ../configure
--disable-optimising $ make $ make test-baseline $ git checkout
T2026-1 $ make test-clean $ make check $ make
Updates:
Status: Started
Labels: Patch-needs_work
Comment #32 on issue 2026 by ianhuli...@gmail.com: Make markup utility
definitions available via new (scm markup-utility-defs) scheme module
http://code.google.com/p/lilypond/issues/detail?id=2026
Caused docs build to fail in
Updates:
Cc: hashas...@gmail.com
Labels: Fixed_2_15_24
Comment #7 on issue 2166 by julien.r...@gmail.com: Copy pdf docs to new
website folder
http://code.google.com/p/lilypond/issues/detail?id=2166
Nice work. Please also close the Rietveld issue.
Comment #16 on issue 695 by ahawry...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
Looks great, you've made my day!
\version 2.15.25
#(ly:set-option 'debug-skylines #t)
\relative c'' {
a\p f g e f d a g
a'(\p f g e f d a g)
Updates:
Status: Verified
Comment #9 on issue 1861 by k-ohara5...@oco.net: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861
The error message did not appear with the commit that fixed this issue, but
later with
On Wed, Jan 11, 2012 at 6:57 AM, -Eluze elu...@gmail.com wrote:
compiling a ly file with obviously wrong version number yields
GNU LilyPond 2.15.24
Processing `test2.ly'
Parsing...
error: program too old: 2.15.24 (file requires: 2.15.26)
Interpreting music...
Preprocessing graphical
Status: Accepted
Owner:
New issue 2214 by idragos...@gmail.com: fatal error reported when version
is too old but correct output is still generated
http://code.google.com/p/lilypond/issues/detail?id=2214
compiling a ly file with obviously wrong version number yields
GNU LilyPond 2.15.24
Updates:
Status: Started
Labels: -Fixed_2_15_14
Comment #17 on issue 1846 by k-ohara5...@oco.net: Improves horizontal
spacing of axis groups that SpanBar grobs traverse
http://code.google.com/p/lilypond/issues/detail?id=1846
The follow-up patch, 70fd22ce, enables the code
lilypond at googlecode.com writes:
think I've found the problem. Dot_column::calc_positioning_done, which is
chained to dots as an x_parent_positioning callback, calls position_less.
This is lethal - it looks up unpure Y extents at a time where they need to
be calculated purely. I
Updates:
Status: Invalid
Comment #1 on issue 2214 by gra...@percival-music.ca: fatal error
reported when version is too old but correct output is still generated
http://code.google.com/p/lilypond/issues/detail?id=2214
This is deliberate to avoid misunderstandings in environments like
Comment #12 on issue 2156 by gra...@percival-music.ca: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
ok. Based on this information, and since Julien is actively working on
issue 2125, I am removing the staging-broken-dec-23 and dec-26 branches.
On Wed, Jan 11, 2012 at 12:19:27PM +0100, Janek Warchoł wrote:
2012/1/10 Xavier Scheuer x.sche...@gmail.com:
I guess this message would be more appropriate on lilypond-u...@gnu.org
rather than on the bug reports mailing list. May I suggest you to send
it (again) to this address, thus
Status: Accepted
Owner:
Labels: Type-Critical
New issue 2215 by gra...@percival-music.ca: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
staging-broken-jan-7 contains two commits not in master:
756cc4f4323071a20d55dc2dc77b5623c1a087c4
Updates:
Labels: -Type-Critical Type-Build
Comment #2 on issue 2184 by gra...@percival-music.ca: GUB can't download
netpbm
http://code.google.com/p/lilypond/issues/detail?id=2184
I suppose this doesn't stop somebody from working on lilypond itself, and
we don't have an official
Updates:
Labels: Patch-review
Comment #5 on issue 2206 by lilypond...@gmail.com: Patch: Let \footnote do
the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob
http://code.google.com/p/lilypond/issues/detail?id=2206#c5
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #16 on issue 2104 by lilypond...@gmail.com: Patch: Fix .dep file
from lilypond-book when include paths are involved.
http://code.google.com/p/lilypond/issues/detail?id=2104#c16
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #10 on issue 2125 by lilypond...@gmail.com: Patch: Build: Don't
rebuild everything each time unless necessary.
http://code.google.com/p/lilypond/issues/detail?id=2125#c10
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #2 on issue 2210 by lilypond...@gmail.com: Patch: Build: Top-level
GNUmakefile
http://code.google.com/p/lilypond/issues/detail?id=2210#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Updates:
Labels: Patch-review
Comment #6 on issue 2209 by lilypond...@gmail.com: lilypond-book creates
uncompilable latex files (windows)
http://code.google.com/p/lilypond/issues/detail?id=2209#c6
Patchy the autobot says: LGTM.
___
Updates:
Summary: error in doc build should point to
build/Documentation/out-www/DocName.log
Comment #5 on issue 2099 by gra...@percival-music.ca: error in doc build
should point to build/Documentation/out-www/DocName.log
http://code.google.com/p/lilypond/issues/detail?id=2099
to
Comment #15 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
The patch from 4 weeks has been uploaded to dev/cg-branches
___
bug-lilypond
Comment #33 on issue 2026 by d...@gnu.org: Make markup utility definitions
available via new (scm markup-utility-defs) scheme module
http://code.google.com/p/lilypond/issues/detail?id=2026
Given the scope of this patch series and the history of applying it,
wouldn't it make sense to check
Comment #8 on issue 1405 by plros...@gmail.com: Web: website Google
search-bar should allow to search the website.
http://code.google.com/p/lilypond/issues/detail?id=1405
Just for the record, +foo doesn't work anymore, use foo in quotes. The
updated search would be:
Updates:
Labels: Patch-new
Comment #7 on issue 2180 by mts...@gmail.com: beams are detached from stems
http://code.google.com/p/lilypond/issues/detail?id=2180#c7
Sketch for DotColumn not triggering vertical alignment.
http://codereview.appspot.com/5538049
60 matches
Mail list logo
