I suppose that a short-term solution would be to simply push the
@bs{} patch. It feels a bit icky, but that's hardly the ickiest
part of lilypond development. And it's inconsistent to kick up a
fuss now when some other languages already do this.
Well, the @example immediately above the
On Sun, Jun 19, 2011 at 11:08:02AM +0200, Frédéric Bron wrote:
Well, the @example immediately above the Program files has a \
in the .itexi file, and proudly displays a \ in the output. Why
does this work inside @example but not @code? Is there any way we
can get @code to act like
Comment #6 on issue 1665 by philehol...@googlemail.com: one-character typo
in predefined-guitar-fretboards.ly
http://code.google.com/p/lilypond/issues/detail?id=1665
Or new tags. Or change the default sort order. Or a few other things like
that concerning the way the project itself is
Comment #7 on issue 1665 by percival.music.ca: one-character typo in
predefined-guitar-fretboards.ly
http://code.google.com/p/lilypond/issues/detail?id=1665
Anybody can add a new tag; only admins can make a registered tag. The
difference is whether it's displayed with green text or brown.
On 19 June 2011 12:57, Michael Hendry hendry.mich...@gmail.com wrote:
The following code demonstrates the fault. The resulting midi file consists of
twelve notes, ascending a major scale from C to G', instead of the expected
sixteen notes.
Please read the doc and use \unfoldRepeats .
Michael Hendry hendry.michael at gmail.com writes:
The following code demonstrates the fault. The resulting midi file consists of
twelve notes, ascending a major scale from C to G', instead of the expected
sixteen notes.
\version 2.12.3
\score {
\repeat volta 2
{c4 d e f}
\alternative
On Sun, Jun 19, 2011 at 01:03:45PM +, Michael Hendry wrote:
I'm trying to think of a situation where playing the second-time ending
immediately after the first-time one would be desirable. I suppose that it
would
be helpful if midi output is being used as a proof-reading assistant, to
Am Sonntag, 19. Juni 2011, 15:26:02 schrieb Graham Percival:
On Sun, Jun 19, 2011 at 01:03:45PM +, Michael Hendry wrote:
I'm trying to think of a situation where playing the second-time ending
immediately after the first-time one would be desirable. I suppose that
it would be helpful if
The following code gives an unaesthetic beam slope with 2.14 (2.15)
whereas the result was good with 2.12 (see attachments).
2.14.1 (2.15.2) gives the following warning:
warning: no viable initial configuration found: may not find good
beam slope
\score {
\new PianoStaff
\new Staff =
Am Sonntag, 19. Juni 2011, 16:55:25 schrieben Sie:
On Sun, Jun 19, 2011 at 04:21:55PM +0200, Reinhold Kainhofer wrote:
Still, it would often be useful to have a global flag to switch on/off
repeat expansion for midi globally. That would be extremely useful in
particular for tremolo repeats
On Sun, Jun 19, 2011 at 04:21:55PM +0200, Reinhold Kainhofer wrote:
Still, it would often be useful to have a global flag to switch on/off repeat
expansion for midi globally. That would be extremely useful in particular for
tremolo repeats (but also for ordinary volta repeats sometimes)!
Xavier Scheuer x.sche...@gmail.com wrote in message
news:BANLkTimYLP-bm9FZJevA=brtqp8oh6n...@mail.gmail.com...
The following code gives an unaesthetic beam slope with 2.14 (2.15)
whereas the result was good with 2.12 (see attachments).
2.14.1 (2.15.2) gives the following warning:
warning: no
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1702 by philehol...@googlemail.com: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
Reported by Xavier Scheuer
The following code gives an unaesthetic beam slope with 2.14
Hello
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Graham
Percival [gra...@percival-music.ca]
Sent: 19 June 2011 10:32
To: Frédéric Bron
Cc: bug-lilypond
Subject: Re:
On Sun, Jun 19, 2011 at 06:57:55PM +, James Lowe wrote:
I tried to 'git am' the patch file and got an error 'Patch format detection
failed'.
I've downloaded it via three different methods (in case it was my mail
client) but I cannot apply this to push.
Check the very beginning of the
I tried to 'git am' the patch file and got an error 'Patch format detection
failed'.
I've downloaded it via three different methods (in case it was my mail
client) but I cannot apply this to push.
Sorry, it just produced with diff -u
The one attached is a proper git patch.
Frédéric
Frederic,
From: Frédéric Bron [frederic.b...@m4x.org]
Sent: 19 June 2011 20:32
To: James Lowe
Cc: Graham Percival; bug-lilypond
Subject: Re: missing backslash before Program Files in
http://www.lilypond.org/windows.html
I tried to 'git am' the patch file
Updates:
Status: Invalid
Comment #1 on issue 1702 by k-ohara5...@oco.net: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
The staff-separation was intentionally reduced for 2.14.
LilyPond would normally give the beamed sets a uniform stem direction,
but
Xavier Scheuer x.scheuer at gmail.com writes:
\new PianoStaff
\new Staff = up {
The default spacing between staves was reduced for version 2.14, to 9 staff-
spaces from the center of one staff to the next.
The method to increase it is a little awkward:
\new PianoStaff \with {
Frédéric,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of James Lowe
[james.l...@datacore.com]
Sent: 19 June 2011 20:44
To: Frédéric Bron
Cc: bug-lilypond
Subject: RE: missing
Comment #2 on issue 1702 by pkx1...@gmail.com: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702
Would it help with an @knownissue or some line in the doc...say in here:
21 matches
Mail list logo
