markpole...@gmail.com writes:
On 2014/06/06 09:29:03, Mark Polesky wrote:
Please review this new patch. I'm not entirely sure this
is the right approach, so I may need some advice here.
This patch has gone through the review/countdown process without a
single comment or review, but I'm not
I am not sure this is the best/correct method for the snippets.
Shouldn't you be editing those in ../snippets/new/.. and then using
makelsr.py to 'update' the snippets in the usual way? Else if someone
comes and edits a snippet in new *after* this patch, all your work is
undone as the 'new'
Hello,
3948
http://code.google.com/p/lilypond/issues/detail?id=3948q=label%3APatch-countdown%20OR%20label%3APatch-waiting%20OR%20label%3APatch-review%20OR%20label%3APatch-new%20OR%20label%3APatch-pushsort=patchcolspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified
- Original Message -
From: pkx1...@gmail.com
To: markpole...@gmail.com; lemzw...@googlemail.com
Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org
Sent: Saturday, June 14, 2014 10:43 AM
Subject: Re: Issue 3951: Fix broken LSR links in docs. (issue 102410043
On 2014/06/14 10:03:46, mail_philholmes.net wrote:
I would suggest correcting the links in the Documentation, but not the
snippets themselves. The links in the snippets are not really visible
(commented out) and, as James says, are over-written with an LSR
import.
Fair enough. I
Reviewers: ,
Message:
Please review
Description:
Color and/or parenthesize single dots in fret-diagrams
Issue 2752
Makes it possible to color and/or parenthesize single dots in
fret-diagram-verbose
Introducing two properties for use in fret-diagram-details
- fret-label-horizontal-offset
https://codereview.appspot.com/102450043/diff/1/Documentation/notation/fretted-strings.itely
File Documentation/notation/fretted-strings.itely (right):
https://codereview.appspot.com/102450043/diff/1/Documentation/notation/fretted-strings.itely#newcode1002
ccing Dev list as I think this might be more pertinent there.
James
On 12/04/14 14:22, Felix Janda wrote:
Hi,
say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.
On 12/04/14 14:22, Felix Janda wrote:
Hi,
say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.
\upbow is treated by lilypond as an articulation, but the other
James pkx1...@gmail.com writes:
On 12/04/14 14:22, Felix Janda wrote:
Hi,
say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.
\upbow is treated by lilypond as an
On 2014/06/14 06:58:52, dak wrote:
On 2014/06/06 09:29:03, Mark Polesky wrote:
... Ideally, if the user has already
modified some of those values, I'd like to base the new scaled values
on
the user's choices, and not base them on the LilyPond default values.
If that's possible at all, I don't
markpole...@gmail.com writes:
On 2014/06/14 06:58:52, dak wrote:
On 2014/06/06 09:29:03, Mark Polesky wrote:
... Ideally, if the user has already
modified some of those values, I'd like to base the new scaled values
on
the user's choices, and not base them on the LilyPond default values.
David Kastrup wrote:
James pkx1...@gmail.com writes:
On 12/04/14 14:22, Felix Janda wrote:
Hi,
say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.
\upbow is
13 matches
Mail list logo
