On 21 juin 2012, at 21:16, Karol Majewski wrote:
> I think I have found a bug. It's related to metronome mark in SVG output.
> Normally, there is one space before equality sign. In SVG output there is
> no space. Take a look at the example.
Thank you for the report, Karol.
Have you tried to visu
On 10 juin 2012, at 15:16, Federico Bruni wrote:
> I've started using \footnote today, so I might miss something.
> Here the footnote is printed twice, first in Staff, then in TabStaff:
>
> \version "2.15.40"
> #(set-default-paper-size "a8landscape")
> \header { tagline = ##f }
>
> music = \rel
On 7 juin 2012, at 07:36, Federico Bruni wrote:
> Il 04/06/2012 09:11, m...@apollinemike.com ha scritto:
>> On 4 juin 2012, at 08:05, David Kastrup wrote:
>>
>>> Federico Bruni writes:
>>>
>>>> Another report about slurs and TabStaff.
>>
On 7 juin 2012, at 07:36, Federico Bruni wrote:
> Il 04/06/2012 09:11, m...@apollinemike.com ha scritto:
>> On 4 juin 2012, at 08:05, David Kastrup wrote:
>>
>>> Federico Bruni writes:
>>>
>>>> Another report about slurs and TabStaff.
>>
On 4 juin 2012, at 08:05, David Kastrup wrote:
> Federico Bruni writes:
>
>> Another report about slurs and TabStaff.
>> IIUC, now slurs connect note heads in polyphony (instead of stems).
>> I _think_ that it's a desired output.
>
> Frankly, it does not look like an improvement to me on the no
On 22 mai 2012, at 19:17, JD Duncan wrote:
>> I'm not top posting.
>
> The following snippet shows a measure where the TupletNumber has good
> placement
> in 2.14.2 but strange placement in 2.15.38.
>
> JD
>
>
> \language english
>
> Score begins here
> \parallelMusic #'(pianoRH dyna
On 11 mai 2012, at 16:39, Trevor Daniels wrote:
>
> m...@apollinemike.com Friday, May 11, 2012 3:22 PM
>
>
>> On 11 mai 2012, at 16:13, David Kastrup wrote:
>>
>>> Mike Solomon writes:
>>>
>>>>> I'm not top posting.
>&g
On 11 mai 2012, at 16:13, David Kastrup wrote:
> Mike Solomon writes:
>
>>> I'm not top posting.
>>
>> \relative c' {
>> \set fingeringOrientations = #'(right)
>> 8
>> }
>>
>> Results in flag-on-number and number-on-number collisions.
>
> Regression?
>
Same result in 2.14.2 and 2.15.35.
On Apr 20, 2012, at 7:40 AM, James wrote:
> Hello,
>
> On 20 April 2012 00:40, Nick Payne wrote:
>> The documentation at
>> http://lilypond.org/doc/v2.15/Documentation/notation/creating-footnotes for
>> both automatic and manual footnotes says that the \footnote command must
>> come *before* the
On Apr 3, 2012, at 1:10 PM, Phil Holmes wrote:
>
> We need to check what the script is doing and how it responds to failing
> snippets like this. I'm not in a position to do this right now, but let's
> not forget it's there. I've put it on the tracker as
> http://code.google.com/p/lilypond/i
On Apr 3, 2012, at 1:26 AM, Thomas Morley wrote:
> Hi,
>
> Seba just informed me that the "Contemporary vibrato" snippet is not
> compiling.
>
Contemporary vibrato is a total hack (it was one of the 1st things I wrote in
LilyPond). It's a miracle that it ever compiled in the first place. I
On Mar 1, 2012, at 4:12 PM, lilyp...@googlecode.com wrote:
>
> Comment #90 on issue 2148 by d...@gnu.org: vertical skylines should use
> stencil integrals
> http://code.google.com/p/lilypond/issues/detail?id=2148
>
> If transparency is not supposed to have an impact anymore, why do we still
>
On Mar 1, 2012, at 3:12 PM, lilyp...@googlecode.com wrote:
>
> Comment #28 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working
> http://code.google.com/p/lilypond/issues/detail?id=2338
>
> Right. I'll contact Christian and ask him to tar up his dev directory then.
>
> Otherwise, is
On Feb 7, 2012, at 2:33 AM, Thomas Morley wrote:
> With "2.15.24" the cross-staff-glissando doesn't work any more.
> 2.14.2-output was ok.
>
> \version "2.15.24"
>
> \new PianoStaff <<
> \new Staff = "right" {
> e'''2\glissando
> \change Staff = "left"
>
> a,,\glissando
> \change Staff
On Feb 6, 2012, at 12:24 PM, Werner LEMBERG wrote:
>>
>> New issue 2293 by mts...@gmail.com: Patch: Gets rid of oval stencil
>> http://code.google.com/p/lilypond/issues/detail?id=2293
>>
>> Gets rid of oval stencil
>>
>> http://codereview.appspot.com/5630064
>
> LGTM, together with the other o
On Jan 31, 2012, at 9:14 PM, Francisco Vila wrote:
> 2012/1/31 Pavel Roskin :
>>> Various users have requested the same in the past.
>>
>> I know. Perhaps it's time to have an issue in the bug tracker.
>
> Definitely.
>
>> Once there is an issue in the tracker, it should be possible to attach
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
On Jan 18, 2012, at 1:28 PM, lilyp...@googlecode.com wrote:
> Updates:
> Status: Started
>
> Comment #6 on issue 2229 by d...@gnu.org: Patch: Broadcast articulations not
> in EventChord
> http://code.google.com/p/lilypond/issues/detail?id=2229
>
> Hi Mike,
> let me see whether I get this
Will do.
Cheers,
MS
On Jan 9, 2012, at 1:33 PM, Neil Puttock wrote:
> On 9 January 2012 12:27, Neil Puttock wrote:
>
>> Hmm, I guess this is my fault. We had a bug with Y-offset positioning
>> when using custom staves, so I revised the offset-callback.
>>
>> Will try to check it out later.
>
On Jan 9, 2012, at 1:20 PM, James wrote:
> hello,
>
> On 9 January 2012 11:55, Thomas Morley wrote:
>> With "2.14.2" and "2.15.2" the BreathingSign isn't positioned correct,
>> while using changed staff-size or (default) TabStaff.
>> 2.12.3-behaviour was accurate.
>>
>> %\version "2.12.3"
>> \v
On Jan 6, 2012, at 10:49 PM, Trevor Daniels wrote:
>
>> Comment #13 on issue 1933 by m...@apollinemike.com: Lilypond-book requires
>> msvcrt again
>> http://code.google.com/p/lilypond/issues/detail?id=1933
>>
>> I think I may have found a one-stop-shopping solut
On Jan 4, 2012, at 7:15 PM, m...@apollinemike.com wrote:
> On Jan 4, 2012, at 6:53 PM, Trevor Daniels wrote:
>
>> Carl
>>
>> Thanks for looking at this. A month or so ago my laptop broke and I now
>> have a new one, with nominally the same OS (Windows Vista) bu
On Jan 4, 2012, at 8:17 PM, Keith OHara wrote:
> On Tue, 03 Jan 2012 10:10:55 -0800, wrote:
>
>> Comment #13 on issue 1948 by PhilEHolmes: Windows install clobbered system
>> http://code.google.com/p/lilypond/issues/detail?id=1948
>>
>> OK - it looks like there is nsis code designed to delete t
On Jan 4, 2012, at 6:53 PM, Trevor Daniels wrote:
> Carl
>
> Thanks for looking at this. A month or so ago my laptop broke and I now have
> a new one, with nominally the same OS (Windows Vista) but at a different
> level. I haven't tried lilypond-book since then, so I've just downloaded
> 2.
On Jan 2, 2012, at 1:55 PM, Karim Haddad wrote:
>
> Hi,
>
> I don't think this was reported. But in the latest dev version it appears
> that \override Stem #'flag = #modern-straight-flag is not working anymore
> ?
> version : 2.15.23-1
> MacosX 10.6.x
>
Hey Karim,
It should be Flag #'stencil
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
On Dec 25, 2011, at 1:48 PM, James wrote:
> Phil (mike)
>
> On 2 December 2011 07:16, m...@apollinemike.com wrote:
>> Le Dec 1, 2011 à 6:21 PM, Phil Holmes a écrit :
>>
>>> "Christopher Schlosser" wrote in message
>>> news:loom.2030t21340
On Dec 17, 2011, at 4:39 PM, Thomas Morley wrote:
> Hi,
>
> this doesn't print flags with "2.15.20", but it does with "2.14.2".
>
>
> \version "2.14.2"
> %\version "2.15.20"
> \new TabStaff { \tabFullNotation c8 }
>
>
> Cheers,
> Harm
Thanks.
There is a patch up to fix this as
http://code
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
Le Dec 7, 2011 à 1:07 PM, Eluze a écrit :
> this is described in
> http://lilypond.org/doc/v2.15/Documentation/usage/common-errors#Common-errors
>
> it points to the fact that there are "… two \relative blocks, which each
> implicitly create Staff and Voice blocks."
>
> the following example cr
Le Dec 2, 2011 à 10:41 AM, lilyp...@googlecode.com a écrit :
>
> So Mike: can you recheck your 5ac2664c2207e8dfa1734d786e5c7b214b275521
> checkin using --no-optimize or whatever else it was we used to check for
> undead objects?
I'm a bit short on time now, but I'll do my best to check it in t
Le Dec 1, 2011 à 6:21 PM, Phil Holmes a écrit :
> "Christopher Schlosser" wrote in message
> news:loom.2030t213409-...@post.gmane.org...
>>> I'm not top posting.
>>
>> %This is e.g. a problem for engraving a choral piece with barlines in
>> mensural
>> style. Maybe this is a special case o
On Nov 26, 2011, at 11:28 PM, m...@apollinemike.com wrote:
> On Nov 26, 2011, at 10:19 PM, Keith OHara wrote:
>
>> On Sat, 26 Nov 2011 00:38:50 -0800, wrote:
>>
>>> Keith,
>>> retested.
>>>
>> Sorry to call you by the wrong name, James. M
On Nov 26, 2011, at 10:19 PM, Keith OHara wrote:
> On Sat, 26 Nov 2011 00:38:50 -0800, wrote:
>
>> Keith,
>> retested.
>>
> Sorry to call you by the wrong name, James. My eyes saw pkx166h and my brain
> though "p h? no that's James" but my fingers were already typed Phil.
>
> I still seems s
On Nov 23, 2011, at 8:09 AM, lilyp...@googlecode.com wrote:
>
> Comment #9 on issue 2047 by d...@gnu.org: Patch: Add \accidentalStyle command
> http://code.google.com/p/lilypond/issues/detail?id=2047
>
> Tsk tsk tsk. Currently working on the documention, and it is rather stupid
> that we have
On Nov 15, 2011, at 11:13 PM, lilyp...@googlecode.com wrote:
> Updates:
> Labels: -Patch-countdown Patch-push
>
> Comment #30 on issue 2000 by colinpkc...@gmail.com: Patch: Fixes NoteColumn
> vs SpanBar collisions.
> http://code.google.com/p/lilypond/issues/detail?id=2000
>
> Counted down
On Nov 17, 2011, at 3:22 PM, lilyp...@googlecode.com wrote:
>
> Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
> intermittently
> http://code.google.com/p/lilypond/issues/detail?id=1723
>
> Previous comment 9 was a wrong lead, just a case of obfuscate programming.
On Nov 8, 2011, at 8:00 AM, Trevor Daniels wrote:
>
>> New issue 2029 by mts...@gmail.com: Patch: Adds some info about pure
>> properties to the CG.
>> http://code.google.com/p/lilypond/issues/detail?id=2029
>>
>> Adds some info about pure properties to the CG.
>>
>> http://codereview.appspot.c
On Oct 29, 2011, at 7:19 PM, lilyp...@googlecode.com wrote:
> Updates:
> Labels: -Priority-Medium
>
> Comment #2 on issue 1874 by pkx1...@gmail.com: some stems are no longer
> transparent in the docs
> http://code.google.com/p/lilypond/issues/detail?id=1874
>
> Mike I don't know if your r
On Oct 28, 2011, at 3:52 PM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Oct 28, 2011, at 3:18 PM, David Kastrup wrote:
>>
>>> "m...@apollinemike.com" writes:
>>>
>>>> Sorry for the oversight. Would
On Oct 28, 2011, at 3:18 PM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> Sorry for the oversight. Wouldn't it just be easier to commit a new
>> commit with the change in version number?
>
> Sure, that's certainly possible. However,
On Oct 28, 2011, at 3:06 PM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Oct 28, 2011, at 2:38 PM, David Kastrup wrote:
>>
>>> "m...@apollinemike.com" writes:
>>>
>>>> On Oct 28, 2011, at 2:11 PM, lilyp.
On Oct 28, 2011, at 2:38 PM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Oct 28, 2011, at 2:11 PM, lilyp...@googlecode.com wrote:
>>
>>>
>>> Comment #8 on issue 1981 by d...@gnu.org: Patch: Adds Scheme
>>> functi
On Oct 28, 2011, at 2:11 PM, lilyp...@googlecode.com wrote:
>
> Comment #8 on issue 1981 by d...@gnu.org: Patch: Adds Scheme function for
> spring constructor.
> http://code.google.com/p/lilypond/issues/detail?id=1981
>
> You forgot to rebase when pulling from dev/staging. I took the liberty o
On Oct 28, 2011, at 10:57 AM, Nick Payne wrote:
> I'm using glissandi to indicate slides in fingering. The following code
> should give me a glissando between the fingering digits (it did in older
> versions), but on 2.15.15 I get no glissando at all:
>
> \version "2.15.15"
>
> \relative c''
On Oct 25, 2011, at 10:06 AM, m...@apollinemike.com wrote:
> On Oct 25, 2011, at 5:32 AM, Keith OHara wrote:
>
>> There are lots of broken beams in Scriabin's first prelude
>> <http://imslp.org/wiki/24_Preludes,_Op.11_(Scriabin,_Aleksandr)>
>> The ori
errata: more note flat = more not flat
On Oct 25, 2011, at 10:06 AM, m...@apollinemike.com wrote:
> On Oct 25, 2011, at 5:32 AM, Keith OHara wrote:
>
>> There are lots of broken beams in Scriabin's first prelude
>> <http://imslp.org/wiki/24_Preludes,_Op.11_(Scriabin,_A
On Oct 24, 2011, at 6:01 AM, lilyp...@googlecode.com wrote:
> Updates:
> Labels: Patch-review
>
> Comment #2 on issue 1986 by percival.music...@gmail.com: Patch: Fixes slope
> errors from incorrect X extents in Beam::print.
> http://code.google.com/p/lilypond/issues/detail?id=1986#c2
>
>
On Oct 22, 2011, at 11:55 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Oct 21, 2011, at 6:15 PM, David Kastrup wrote:
>>
>>>
>>> commit 1d9a73b13ee576d28c0f41f5b243f2ebb1ff9fcf
>>> Author: Mike Solomon
>>
On Oct 21, 2011, at 6:15 PM, David Kastrup wrote:
>
> commit 1d9a73b13ee576d28c0f41f5b243f2ebb1ff9fcf
> Author: Mike Solomon
> Date: Fri Oct 21 09:03:43 2011 +0200
>
>Implements consistent beam slopes across line breaks.
>
> says
>
>To turn on this feature, use \override Beam #'cons
On Oct 19, 2011, at 4:03 AM, lilyp...@googlecode.com wrote:
>
> Comment #14 on issue 1844 by colinpkc...@gmail.com: Changes variable names in
> include/beam-scoring-problem.hh and beam-quanting.cc
> http://code.google.com/p/lilypond/issues/detail?id=1844
>
> Does this still need work, Mike? Jam
On Oct 18, 2011, at 12:38 PM, lilyp...@googlecode.com wrote:
>
> Comment #13 on issue 1567 by pkx1...@gmail.com: Add documentation for
> footnotes
> http://code.google.com/p/lilypond/issues/detail?id=1567
>
> I'm making headway into documenting the auto and (I prefer) manual
> footnote commands
On Oct 17, 2011, at 1:12 PM, m...@apollinemike.com wrote:
> On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
>
>> On 17 October 2011 11:41, Graham Percival wrote:
>>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>>> On 17 O
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On Oct 17, 2011, at 9:30 AM, Peekay Ex wrote:
> Mike
>
> On Mon, Oct 17, 2011 at 8:12 AM, m...@apollinemike.com
> wrote:
>> On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
>>
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
>>>&g
On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>
>> However, and this is for Phil: could we not simply 'deprecate' the
>> snippet(s) like we do with any that won't work (properly) in later
>> versions, and actually I think it was Mike that a week or s
On Oct 17, 2011, at 12:43 AM, Graham Percival wrote:
> On Sun, Oct 16, 2011 at 11:02:22PM +0200, m...@apollinemike.com wrote:
>>
>> I think that by running convert-ly via the script in 10.9.4,
>> duplicate Flag #'transparent statements will be issued (every
>
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical Regression
>
> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
> http://code.google.com/p/lilypond/issues/detail?id=1971
>
> The NR
> (http://lilypond.org/
On Oct 16, 2011, at 10:07 PM, Graham Percival wrote:
> On Sun, Oct 16, 2011 at 12:13:27PM +0200, m...@apollinemike.com wrote:
>>
>> Is there a way to run convert-ly on the docs to eliminate this sorta problem?
>
> Yes. By some incredible coincidence, it is dis
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical Regression
>
> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
> http://code.google.com/p/lilypond/issues/detail?id=1971
>
> The NR
> (http://lilypond.org/
On Oct 10, 2011, at 9:22 AM, lilyp...@googlecode.com wrote:
>
> Comment #5 on issue 1591 by d...@gnu.org: doc: midi output is channel-voice
> http://code.google.com/p/lilypond/issues/detail?id=1591
>
> More like "second stab at getting Percival mad". Let me guess: you are using
> the new git-c
On Oct 4, 2011, at 8:49 AM, lilyp...@googlecode.com wrote:
> Updates:
> Labels: -Patch-new Patch-needs_work
>
> Comment #3 on issue 1791 by pkx1...@gmail.com: footnote numbering is 'out of
> order' when using multiple staves in a system
> http://code.google.com/p/lilypond/issues/detail?id=
On Oct 3, 2011, at 10:10 AM, lilyp...@googlecode.com wrote:
>
> Comment #10 on issue 737 by pkx1...@gmail.com: Enhancement: support for
> footnotes and/or endnotes.
> http://code.google.com/p/lilypond/issues/detail?id=737
>
> Just doc required I think
>
> This is started (honest!) by myself
>
On Oct 2, 2011, at 7:27 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Ugly
>
> New issue 1950 by brownian.box: \mark after \stopStaff forces extension of
> staff symbol
> http://code.google.com/p/lilypond/issues/detail?id=1950
>
> \relative c'' {
> c1
> \s
On Sep 30, 2011, at 8:50 AM, m...@apollinemike.com wrote:
> On Sep 30, 2011, at 8:24 AM, lilyp...@googlecode.com wrote:
>
>> Updates:
>> Status: Fixed
>>
>> Comment #12 on issue 1846 by mts...@gmail.com: Improves horizontal spacing
>> of axis groups
On Oct 1, 2011, at 11:47 AM, lilyp...@googlecode.com wrote:
> Updates:
> Status: Accepted
> Labels: -fixed_2_15_13
>
> Comment #4 on issue 1926 by philehol...@googlemail.com: 2.15.12 processing
> speed problems
> http://code.google.com/p/lilypond/issues/detail?id=1926
>
> No. On my
On Sep 30, 2011, at 7:43 PM, Peekay Ex wrote:
> hello
>
> On Fri, Sep 30, 2011 at 6:39 PM, Jay Anderson wrote:
>> 6 x 9 in. isn't currently available. I haven't found a standard name
>> for this size. Lulu calls it 'US Trade',
>> http://en.wikipedia.org/wiki/Book_size calls it 'octavo'. In any c
On Sep 30, 2011, at 8:24 AM, lilyp...@googlecode.com wrote:
> Updates:
> Status: Fixed
>
> Comment #12 on issue 1846 by mts...@gmail.com: Improves horizontal spacing of
> axis groups that SpanBar grobs traverse
> http://code.google.com/p/lilypond/issues/detail?id=1846
>
> Fixed with 20670
On Sep 29, 2011, at 5:33 AM, lilyp...@googlecode.com wrote:
> Updates:
> Labels: -Patch-countdown Patch-push
>
> Comment #3 on issue 1921 by colinpkc...@gmail.com: Creates convert-ly rules
> for flag syntax changes
> http://code.google.com/p/lilypond/issues/detail?id=1921
>
> Counted down
On Jul 21, 2011, at 11:10 AM, lilyp...@googlecode.com wrote:
>
> Comment #17 on issue 34 by reinhold...@gmail.com: Grace synchronization
> http://code.google.com/p/lilypond/issues/detail?id=34
>
> Comment by Keith O'Hara on bug-lilypond:
>
>> However, in my eyes we need to distinguish the event
On Sep 24, 2011, at 12:43 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical Regression
>
> New issue 1926 by philehol...@googlemail.com: 2.15.12 processing speed
> problems
> http://code.google.com/p/lilypond/issues/detail?id=1926
>
> On my system, 2.15
On Sep 22, 2011, at 10:31 AM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Needs-evidence Type-Ugly
>
> New issue 1915 by brownian.box: slurs don't avoid other voices
> http://code.google.com/p/lilypond/issues/detail?id=1915
>
> Reported by -Eluze,
> http://lists.gnu
On Sep 22, 2011, at 9:25 AM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Ugly
>
> New issue 1912 by brownian.box: Horizontal spacing depends on stem 'direction
> http://code.google.com/p/lilypond/issues/detail?id=1912
>
> Reported by Trevor Daniels,
> http://li
On Sep 19, 2011, at 5:22 PM, Neil Puttock wrote:
> On 19 September 2011 16:16, David Kastrup wrote:
>
>> The debug symbols should not affect code speed, and they are present in
>> the unoptimized build, anyway, unless you are talking about something
>> completely different from what I think you
On Sep 19, 2011, at 4:04 PM, Neil Puttock wrote:
> On 19 September 2011 13:05, m...@apollinemike.com
> wrote:
>
>> Perhaps create two new make options:
>>
>> make unsafe-test-baseline
>>
>> and
>>
>> make unsafe-check
>>
>> T
On Sep 19, 2011, at 2:01 PM, lilyp...@googlecode.com wrote:
>
> Comment #2 on issue 1905 by n.putt...@gmail.com: Add note to CG 9.3
> 'Compiling reg tests' to add --disable-optimising when using autogen.sh or
> configure
> http://code.google.com/p/lilypond/issues/detail?id=1905
>
> Won't your
On Sep 18, 2011, at 2:08 AM, lilyp...@googlecode.com wrote:
> Updates:
> Status: Fixed
> Owner: reinhold...@gmail.com
> Labels: fixed_2_15_12
>
> Comment #2 on issue 1008 by reinhold...@gmail.com: Some warning/error
> messages are not prefixed with 'warning:'/'error:'
> http://
On Sep 11, 2011, at 11:30 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical
>
> New issue 1881 by n.putt...@gmail.com: Multiple cyclic dependency errors for
> Beam/Stem
> http://code.google.com/p/lilypond/issues/detail?id=1881
>
> Following commit 64652
On Aug 2, 2011, at 11:15 PM, David Kastrup wrote:
> James Lowe writes:
>
>> From: lilypond-user-bounces+james.lowe=datacore@gnu.org
>> [lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of
>> Tim Reeves [tim.ree...@tokamerica.com]
>> Sent: 02 August 2011 19:56
>> To: lilypond-
On Jul 27, 2011, at 12:22 PM, lilyp...@googlecode.com wrote:
> Updates:
> Owner: ---
> Labels: -Priority-High -Patch-needs_work Priority-Medium Patch-abandoned
>
> Comment #6 on issue 36 by pkx1...@gmail.com: collision cresc and kneed beams
> http://code.google.com/p/lilypond/issues/d
On Jul 22, 2011, at 12:24 PM, lilyp...@googlecode.com wrote:
>
> Comment #1 on issue 1772 by lilyli...@googlemail.com:
> Completion_rest_engraver fails with fractional rests
> http://code.google.com/p/lilypond/issues/detail?id=1772
>
> As Neil Puttock reported Completion_heads_engraver behaves
On Jul 22, 2011, at 9:57 AM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Enhancement Priority-Low
>
> New issue 1773 by pkx1...@gmail.com: Add Footnote_engraver to Staff context
> http://code.google.com/p/lilypond/issues/detail?id=1773
>
> This came out of the
On Jul 21, 2011, at 1:37 PM, Dmytro O. Redchuk wrote:
> On Thu 21 Jul 2011, 13:20 m...@apollinemike.com wrote:
>> \new Voice
>> \with { \remove "Rest_engraver" \consists "Completion_rest_engraver" }
>> { r1*6/4 r2 }
>>
>> This gets me the
\new Voice
\with { \remove "Rest_engraver" \consists "Completion_rest_engraver" }
{ r1*6/4 r2 }
This gets me the attached output.
PastedGraphic-1.pdf
Description: Adobe PDF document
Cheers,
MS___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
On Jul 18, 2011, at 10:14 AM, Bertrand Bordage wrote:
> Hi all,
>
> A bug I noticed years ago :
>
> <<
> { a'4~ a' a'~ a' ~ } \\
> { c' c' c' c' } \\
> { f'~ f' \shiftOff f'~ f' } \\
>>>
>
> Ties should take noteheads from other contexts into account.
>
> Regards,
> Bertrand
I'm loath to
On Jul 4, 2011, at 11:45 AM, Dmytro O. Redchuk wrote:
> On Mon 04 Jul 2011, 15:39 James Harkins wrote:
>> \version "2.14.1"
>>
>> \include "english.ly"
>>
>> \score {
>> \new Staff {
>> \key d \major
>> \numericTimeSignature
>> \time 4/4
>> r4
>> \times 4/5 { 16\< > d'' b''>~ }
>> 16
On May 29, 2011, at 3:00 PM, Carl Sorensen wrote:
> On 5/29/11 5:42 AM, "Hilary Snaden" wrote:
>
>> Phil Holmes wrote:
>>> "Hilary Snaden" wrote in message
>>> news:4de210b3.80...@newearth.demon.co.uk...
Manual beamings of cross-staff note groups are mangled, but
inconsistently. The b
On May 23, 2011, at 4:18 PM, lilyp...@googlecode.com wrote:
>
> Comment #2 on issue 1660 by brownian.box: harmonicOn doesn't work in TabStaff
> http://code.google.com/p/lilypond/issues/detail?id=1660
>
> Should this issue be tagged as Invalid then?
I'd say so. The docstring for harmonicsOn doe
On May 7, 2011, at 1:49 AM, Nick Payne wrote:
> A bar excerpted from the Mertz guitar transcription of Ständchen. When I last
> worked on this score about ten months ago, using 2.13.27, I didn't have the
> problem with the beam on the notes in the middle voice being placed below the
> stem of t
On May 5, 2011, at 2:12 AM, Nick Payne wrote:
> On 05/05/11 13:21, m...@apollinemike.com wrote:
>> On May 4, 2011, at 3:16 PM, Nick Payne wrote:
>>
>>> Latest LP development version has inconsistency. See below.
>>>
>>> \version "2.13.61"
>
On May 4, 2011, at 3:16 PM, Nick Payne wrote:
> Latest LP development version has inconsistency. See below.
>
> \version "2.13.61"
>
> \relative c'' {
>\time 3/4
>\key d \minor
> <<
>{ 8 r r s }
>\\
>{ d, r cis r r4 }
>\\
>{ g'8. f16 g8. bes16 a8. g16 }
> >>
> }
>
On May 2, 2011, at 5:21 AM, lilyp...@googlecode.com wrote:
>
> Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
> http://code.google.com/p/lilypond/issues/detail?id=1612
>
> I have missed something very probably, but: this issue is of type "Collision"
> (not "Doc") st
On Apr 27, 2011, at 11:31 AM, Phil Holmes wrote:
> "James Lowe" wrote in message
> news:ddfaf00dc0c80042bab7bba1b3838af9145f3...@mail-ftl2.datacoresoftware.com...
>> Fwding to email group as I was sent this privately:
>>
>> )-Original Message-
>> )From: Bird [mailto:leader.b...@yahoo.co
On Apr 26, 2011, at 8:02 AM, Nick Payne wrote:
> This code used to work for me about a year ago, but when I try to build it
> using 2.13.60, I get the weird error shown in the console log output at the
> bottom. Is this a bug or not? I'm running 2.13.60 on Ubuntu 10.04 amd64.
>
> %=
> It appears to me right now that chordGlissando is a sufficiently rough hack
> that it should probably be removed from the distribution and just be present
> in the LSR.
+1.
I will have time this weekend to work on an implementation that uses a context
property to control how glissandi are types
On Apr 25, 2011, at 6:14 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> From Damien Pallant:
>>
>> \new Staff {
>> \key ees \major
>> \clef treble
>> \override Staff.NoteCollision #'merge-differently-headed = ##t
&g
>From Damien Pallant:
\new Staff {
\key ees \major
\clef treble
\override Staff.NoteCollision #'merge-differently-headed = ##t
\override Staff.NoteCollision #'merge-differently-dotted = ##t
\relative c' {
<< { r8 g ( bes d-3 ) f4-5 -- ees-4 -- } \\ { s8 g,~ 2. } >>
<< { r8 aes ( bes ees-4 ) f4-5
On Apr 23, 2011, at 4:31 PM, Graham Percival wrote:
> On Sat, Apr 23, 2011 at 03:50:18PM -0400, m...@apollinemike.com wrote:
>> On Apr 23, 2011, at 1:32 PM, Graham Percival wrote:
>>
>>> Confirmed. :(
>>> If I can't fix it in the next hour, I'll add a
That said, the following code still produces the same message:
\version "2.13.59"
<<
\new Staff = "md" \relative c' {
r4 r8 s s2
r4 r8 s s2
r4 e, r2 |
}
\new Staff = "mg" \relative c'' {
b8 f' c' \change Staff = "md" ~
2 \change Staff = "mg" |
\once \override Beam #'collision-
1 - 100 of 112 matches
Mail list logo
