now and then i use this little snippet (
http://lsr.dsi.unimi.it/LSR/Item?id=507
http://lsr.dsi.unimi.it/LSR/Item?id=507 ), but each time i have to figure
out newly how it works…
i suggest to add something like:
… with '\displayLilyMusic \ghostMusic \notes' the ghost voice is written to
the
- Original Message -
From: -Eluze elu...@gmail.com
To: lilypond-devel@gnu.org
Sent: Tuesday, February 15, 2011 8:20 AM
Subject: add \displayLilyMusic to snippet
http://lsr.dsi.unimi.it/LSR/Item?id=507
now and then i use this little snippet (
http://lsr.dsi.unimi.it/LSR/Item?id=507
This snippet of code:
\paper { ragged-right = ##t }
\new Staff { \relative c' { \cadenzaOn \override Beam #'breakable = ##t
\override Beam #'grow-direction = #RIGHT a32 [ b c d e f \bar \break g ] } }
\new Staff { \relative c' { \cadenzaOn \override Beam #'breakable = ##t
\override Beam
The NR, 1.2.6 Special rhythmic concerns, Grace notes, says:
A \grace music expression will introduce special typesetting settings, for
example, to produce smaller type, and set directions. Hence, when
introducing layout tweaks to override the special settings, they should be
placed inside the
Phil
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Phil Holmes
)Sent: 15 February 2011 12:47
)To: lilypond-devel@gnu.org
)Subject: Documentation request
)
)The NR, 1.2.6
Update on http://code.google.com/p/lilypond/issues/detail?id=1517
http://codereview.appspot.com/4172047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From: James Lowe james.l...@datacore.com
To: 'Phil Holmes' m...@philholmes.net; lilypond-devel@gnu.org
Sent: Tuesday, February 15, 2011 1:00 PM
Subject: RE: Documentation request
Phil
)-Original Message-
)From:
On 2011/02/15 07:15:48, Trevor Daniels wrote:
http://codereview.appspot.com/4160048/diff/5001/Documentation/notation/rhythms.itely#newcode2211
Documentation/notation/rhythms.itely:2211: To avoid this problem, the
time
signature can be set in only one
I still prefer should
I don't want to
On 2011/02/15 13:17:01, Bertrand Bordage wrote:
Update on http://code.google.com/p/lilypond/issues/detail?id=1517
I've added this to codereview.
Bertrand, could you upload it to codereview yourself, with a new
codereview issue number? I think the instructions in the Contributor's
Guide are
I do not believe that this is the latest version; could we close this
issue, and put a link to the real version on the google tracker issue
1510 ?
http://codereview.appspot.com/4129053/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
LGTM. I prefer not to fuss about @knownissues, so just push it
when(ever) you think it's good enough.
http://codereview.appspot.com/4160048/diff/11001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
mike at apollinemike.com mike at apollinemike.com writes:
On Feb 14, 2011, at 6:20 AM, Dmytro O. Redchuk wrote:
On Mon 07 Feb 2011, 21:17 Werner LEMBERG wrote:
\header { texidoc =
The beaming algorithm should handle collisions between beams and
grace notes too.
Here is a
On 2011/02/14 23:25:21, Keith wrote:
On Mon, 14 Feb 2011 13:43:37 -0800, mailto:n.putt...@gmail.com
wrote:
My only concern with these changes is the barline avoidance (which
you
mention in the tracker as possibly a good thing). There's one
regtest
which shows the problem: in
Yes, sorry...
I made a new codereview issue : http://codereview.appspot.com/4182056/
...(currently reading the Contributor's Guide again)...
http://codereview.appspot.com/4172047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
percival.music...@gmail.com wrote Saturday, February 05, 2011 6:20
PM
http://codereview.appspot.com/4079064/diff/1/Documentation/notation/pitches.itely#newcode827
Documentation/notation/pitches.itely:827: it may be converted to
its
@notation{retrograde} (written backwards).
I'm not certain
2011/2/14 Keith OHara k-ohara5...@oco.net:
The override below makes the spring stiff enough to avoid this extra check,
so the spring near the accidental is not lenghened. (The override will not
work well in tight layouts.) Does this produce closer to what the good
engravers do?
-Keith
Reviewers: ,
Message:
Add documentation of partcombine functions.
See issue 1518 on the bug tracker.
Description:
DOC: NR 1.5.2 Multiple voices - part combining
Adds explanations and examples of part combine functions to
NR 1.5.2 Multiple voices - Automatic part combining
Patch based on issue
LGTM.
http://codereview.appspot.com/4188056/diff/1/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
http://codereview.appspot.com/4188056/diff/1/Documentation/notation/simultaneous.itely#newcode846
Documentation/notation/simultaneous.itely:846:
Looks good as it is,
better if you can add one markup that Reinhold missed in the example.
http://codereview.appspot.com/4188056/diff/1/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
19 matches
Mail list logo