Status: Accepted
Owner:
Labels: Type-Maintainability
New issue 2089 by gra...@percival-music.ca: dangerous redefinition of SCM s
/ Moment s
http://code.google.com/p/lilypond/issues/detail?id=2089
// in music-sequence.cc, line 144
// variable "s" is redefined. This can be confusing.
// a
Le Dec 8, 2011 à 5:10 PM, lilyp...@googlecode.com a écrit :
> Updates:
> Labels: Patch-needs_work
>
> Comment #22 on issue 460 by lilypond...@gmail.com: bar numbers for broken bars
> http://code.google.com/p/lilypond/issues/detail?id=460#c22
>
> Patchy the autobot says: tuplet-broken.ly go
Updates:
Labels: Patch-new
Comment #23 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c23
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
_
Comment #2 on issue 1964 by gra...@percival-music.ca: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964
given the problems with gcc 4.6, I think we should stick to ubuntu 10.04.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
htt
Status: Accepted
Owner:
Labels: Type-Maintainability
New issue 2088 by gra...@percival-music.ca: pointer confusion with clang++
http://code.google.com/p/lilypond/issues/detail?id=2088
Attempting to compile with clang++, or do a static analysis:
gperciva@chikara:~/src/lilypond/lily$ clang++
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2087 by lilypond...@gmail.com: Patch: Fixes various warnings from
clang++
http://code.google.com/p/lilypond/issues/detail?id=2087
Fixes various warnings from clang++
These changes leave the regtests unchanged.
This is a bra
Updates:
Labels: -Patch-review Patch-needs_work
Comment #12 on issue 409 by colinpkc...@gmail.com: Using whiteout and layer
properties for ties avoiding collision with staff objects
http://code.google.com/p/lilypond/issues/detail?id=409
Graham's comments on Rietveld
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 2077 by colinpkc...@gmail.com: Patch: Provide Scheme
sandbox.
http://code.google.com/p/lilypond/issues/detail?id=2077
Counted down to 20111208
___
bug-lilypond mailing list
Updates:
Labels: -Patch-countdown Patch-needs_work
Comment #8 on issue 2075 by gra...@percival-music.ca: Implement GOP 9 -
behavior of make doc
http://code.google.com/p/lilypond/issues/detail?id=2075
(No comment was entered for this change.)
_
On 08/12/11 19:44, David Kastrup wrote:
Nick Payne writes:
No, I ran "find ~/ -name lilypond" and nothing was found.
env | grep lilypond
is also empty?
Aha! (strikes forehead). That was it. I completely forgot that I had
come across the LILYPOND_DATADIR env variable and experimented to se
wrote in message
news:0-9567054385019064696-10459256515927967800-lilypond=googlecode@googlecode.com...
Status: Accepted
Owner:
CC: d...@gnu.org
New issue 2084 by idragos...@gmail.com: script-accidental avoidance fails
for articulations
http://code.google.com/p/lilypond/issues/detail?
Eluze writes:
> David Kastrup gnu.org> writes:
>>
>> It is also conceivable that this depends on the startup stub of whatever
>> compiler you happened to be using.
>>
>> I know why I don't do Windows.
>>
> anything works:
>
> -dpoint-and-click=#f
> -dpoint-and-click="#f"
> -d"point-and-click=
Updates:
Labels: Patch-needs_work
Comment #22 on issue 460 by lilypond...@gmail.com: bar numbers for broken
bars
http://code.google.com/p/lilypond/issues/detail?id=460#c22
Patchy the autobot says: tuplet-broken.ly goes from nothing to (2). Look,
this is supposed to catch *unintentio
David Kastrup gnu.org> writes:
>
> Eluze gmail.com> writes:
>
> > in
> > http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-
usage#Command-line-options-for-lilypond
> > there are examples using single quotes:
> >
> > lilypond -e '(define-public a 42)'
> > -dpoint-and-click='#f'
Eluze writes:
> in
> http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-usage#Command-line-options-for-lilypond
> there are examples using single quotes:
>
> lilypond -e '(define-public a 42)'
> -dpoint-and-click='#f'
>
> this does not work under windows where you have to use doub
in
http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-usage#Command-line-options-for-lilypond
there are examples using single quotes:
lilypond -e '(define-public a 42)'
-dpoint-and-click='#f'
this does not work under windows where you have to use double quotes!
i suggest to
Comment #21 on issue 460 by gra...@percival-music.ca: bar numbers for
broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
Well, although I ended up dropping the artificial intelligence class, I've
been having a blast with the machine learning class.
http://www.ml-class.org/
Comment #20 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
Patchy's ability to communicate like a human, analyze musical information,
and make musically-informed commentary is astounding.
New patch set up making this not a
Updates:
Labels: Patch-new
Comment #19 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c19
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
_
Comment #18 on issue 460 by lemzw...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
Of course! Everything else is a bug. Mike?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/
Comment #17 on issue 460 by gra...@percival-music.ca: bar numbers for
broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
I've deleted the regtest by now, but there were something like 5 regtests
effected. The single broken bar didn't disturb me as much as
==
(1)==
Comment #16 on issue 460 by lemzw...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
I don't disagree. But: How many regtests do we have with a single broken
bar? Shouldn't we rather disable bar numbers in those tests?
___
Updates:
Labels: Patch-review
Comment #15 on issue 460 by lilypond...@gmail.com: bar numbers for broken
bars
http://code.google.com/p/lilypond/issues/detail?id=460#c15
Patchy the autobot says: LGTM. Patchy isnt going to reject this, but as a
reviewer I want this behavior turned off
Updates:
Labels: Patch-review
Comment #6 on issue 2026 by lilypond...@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#c6
Patchy the autobot says: LGTM.
__
Status: Accepted
Owner: gra...@percival-music.ca
Labels: Type-Maintainability
New issue 2086 by gra...@percival-music.ca: generate gitstats automatically
http://code.google.com/p/lilypond/issues/detail?id=2086
We should generate gitstats automatically as part of the release process.
(in fact,
Updates:
Labels: -Type-Critical Type-Build
Comment #4 on issue 2027 by gra...@percival-music.ca: make website doesn't
have dependencies
http://code.google.com/p/lilypond/issues/detail?id=2027
mitigated in
ce6677cf4036e1d821d69a2f339ebb8ffe7b3681
We'll leave the issue open, because a
Updates:
Labels: -Patch-needs_work Patch-new
Comment #5 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
New patch available for review at http://cod
Hello,
On 8 December 2011 10:50, Eluze wrote:
> Windows has a crappy command line. Try using double quotes " instead of
>> the single quotes ' suggested above.
>>
>
>
> thanks for the hint - it works now!
>
> maybe a hint in "Usage" whould help (is a dokumentatlist listening …)?!
>
No. But we
Updates:
Labels: Patch-new
Comment #14 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c14
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
_
Updates:
Labels: Patch-needs_work
Comment #13 on issue 460 by lilypond...@gmail.com: bar numbers for broken
bars
http://code.google.com/p/lilypond/issues/detail?id=460#c13
Patchy the autobot says: does not apply to master
___
bug-lilypond
Updates:
Labels: Patch-review
Comment #43 on issue 2057 by lilypond...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057#c43
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
b
Windows has a crappy command line. Try using double quotes " instead of
the single quotes ' suggested above.
thanks for the hint - it works now!
maybe a hint in "Usage" whould help (is a dokumentatlist listening …)?!
Eluze
___
bug-lilypond mailing
Comment #42 on issue 2057 by gra...@percival-music.ca: Hairpin hits barline
at line break
http://code.google.com/p/lilypond/issues/detail?id=2057
There are no plans for any more 2.14 releases. The 2.16 release will
happen when the current Critical releases reaches 0.
___
Comment #33 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
Issue 1809 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.
Updates:
Status: Duplicate
Owner: d...@gnu.org
Mergedinto: 1997
Comment #5 on issue 1809 by d...@gnu.org: make test segfaults
http://code.google.com/p/lilypond/issues/detail?id=1809
Actually I fixed this already. Marking it as a duplicate of the fixed
issue.
___
Comment #41 on issue 2057 by prze...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
Great. Sorry for constant complaints. :)
I forgot to add one more thing. Even though I strongly believe that padding
should be always there for hairpin
Updates:
Labels: -Priority-High
Comment #11 on issue 39 by pkx1...@gmail.com: collision flag notehead with
polyphony
http://code.google.com/p/lilypond/issues/detail?id=39
(No comment was entered for this change.)
___
bug-lilypond mailing l
Updates:
Labels: -Priority-High
Comment #13 on issue 139 by pkx1...@gmail.com: tie misinterpreted as a slur
http://code.google.com/p/lilypond/issues/detail?id=139
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lil
Updates:
Labels: -Priority-High
Comment #9 on issue 992 by pkx1...@gmail.com: Tuplets collide with notes
outside the staff
http://code.google.com/p/lilypond/issues/detail?id=992
(No comment was entered for this change.)
___
bug-lilypond ma
Updates:
Owner: ---
Labels: -Priority-High
Comment #1 on issue 1004 by pkx1...@gmail.com: more thought needed for
website integration
http://code.google.com/p/lilypond/issues/detail?id=1004
(No comment was entered for this change.)
___
Updates:
Labels: -Priority-High
Comment #26 on issue 1055 by pkx1...@gmail.com: guile 2.0
http://code.google.com/p/lilypond/issues/detail?id=1055
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
htt
Updates:
Labels: -Priority-High
Comment #4 on issue 1134 by pkx1...@gmail.com: Notes in different voices do
not treat accidentals properly
http://code.google.com/p/lilypond/issues/detail?id=1134
(No comment was entered for this change.)
__
Updates:
Labels: -Priority-High
Comment #1 on issue 1183 by pkx1...@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
Updates:
Labels: -Priority-High
Comment #12 on issue 1208 by pkx1...@gmail.com: Some combination
of 'staff-affinity for two Lyrics may cause unwanted vertical space
http://code.google.com/p/lilypond/issues/detail?id=1208
(No comment was entered for this change.)
Updates:
Labels: -Priority-High
Comment #1 on issue 1388 by pkx1...@gmail.com: Support OpenType font
features
http://code.google.com/p/lilypond/issues/detail?id=1388
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Labels: -Priority-High
Comment #2 on issue 1505 by pkx1...@gmail.com: bendAfter not spanning line
break properly
http://code.google.com/p/lilypond/issues/detail?id=1505
(No comment was entered for this change.)
___
bug-lilypond ma
Updates:
Labels: -Priority-High
Comment #2 on issue 1566 by pkx1...@gmail.com: Flagged notes lose flags
with autobeaming and hidenotes
http://code.google.com/p/lilypond/issues/detail?id=1566
(No comment was entered for this change.)
___
bu
Updates:
Labels: -Priority-High
Comment #4 on issue 1645 by pkx1...@gmail.com: Beam_collision_engraver
sometimes fails on demisemiquavers or shorter notes
http://code.google.com/p/lilypond/issues/detail?id=1645
(No comment was entered for this change.)
__
Updates:
Labels: -Priority-High
Comment #1 on issue 1662 by pkx1...@gmail.com: midi & pdf disagree with
conflicting tempo-changes
http://code.google.com/p/lilypond/issues/detail?id=1662
(No comment was entered for this change.)
___
bug-lil
Updates:
Labels: -Priority-High
Comment #10 on issue 1686 by pkx1...@gmail.com: Compile scheme files to
scm/out when using Guile V2.n. Also load and run .go files if available
http://code.google.com/p/lilypond/issues/detail?id=1686
(No comment was entered for this change.)
Updates:
Labels: -Priority-High
Comment #4 on issue 1713 by pkx1...@gmail.com: Whole note/dotted note
collision in polyphony
http://code.google.com/p/lilypond/issues/detail?id=1713
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Labels: -Priority-High
Comment #4 on issue 1718 by pkx1...@gmail.com: Slur collides with stems
http://code.google.com/p/lilypond/issues/detail?id=1718
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypo
Updates:
Labels: -Priority-High
Comment #4 on issue 1731 by pkx1...@gmail.com: LilyPond fails to install on
Puppy Linux
http://code.google.com/p/lilypond/issues/detail?id=1731
(No comment was entered for this change.)
___
bug-lilypond mail
Updates:
Labels: -Priority-High
Comment #7 on issue 1806 by pkx1...@gmail.com: Wrong search for translated
docs
http://code.google.com/p/lilypond/issues/detail?id=1806
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Labels: -Priority-High
Comment #17 on issue 1732 by pkx1...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
(No comment was entered for this change.)
_
Updates:
Labels: -Priority-High
Comment #4 on issue 1809 by pkx1...@gmail.com: make test segfaults
http://code.google.com/p/lilypond/issues/detail?id=1809
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gn
Nick Payne writes:
> No, I ran "find ~/ -name lilypond" and nothing was found.
env | grep lilypond
is also empty?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Updates:
Labels: Patch-new
Comment #40 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057#c40
Adds padding between Hairpins and SpanBars.
http://codereview.appspot.com/5438060
___
Comment #12 on issue 694 by pkx1...@gmail.com: Enhancement: easier use of
microtone accidentals
http://code.google.com/p/lilypond/issues/detail?id=694
I'm wondering if this is a 'documentation' issue or not. We don't normally
(IFAICT) make trackers for LSR snippets. So I'm finding it hard t
Updates:
Labels: Type-Ugly
Comment #1 on issue 2084 by pkx1...@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.)
___
bug-lilypon
Comment #11 on issue 409 by pkx1...@gmail.com: Using whiteout and layer
properties for ties avoiding collision with staff objects
http://code.google.com/p/lilypond/issues/detail?id=409
New patch as per Keith's comments uploaded.
http://codereview.appspot.com/5453066/
James
___
Comment #10 on issue 2076 by pkx1...@gmail.com: Doc: improve NR 1.6.3
Instrument names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
Second Draft up (corrections from David)
http://codereview.appspot.com/5448129/
James
_
Updates:
Labels: Patch-new
Comment #12 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c12
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
_
On 08/12/11 18:07, David Kastrup wrote:
Nick Payne writes:
I was using Lilypond with no problems yesterday (2.15.20 on Ubuntu
10.04 amd64). I noticed 2.15.21 on lilypond.org this morning, so I
downloaded the Linux 64 version, ran uninstall-lilypond, and installed
2.15.21. On any attempt to run
64 matches
Mail list logo
