Re: Make \upbow an empty command + Segmentation fault

2014-06-15 Thread Felix Janda 
Dan Eble wrote:
[..]
 I’m sorry I haven’t spent time to thoroughly understand your needs,
 but it sounds like there is a chance that something derived from this
 (which I have actually used) would help:
 
 stripArticulation =
 #(define-music-function
   (parser location music) (ly:music?)
   (music-filter
(lambda (m) (not (eq? (ly:music-property m 'name) 'ArticulationEvent)))
music))
 
 Rather than redefining \upbow, use \stripBowings \yourMusic to filter
 out the articulations you don’t want to see.

Thanks. It seems that after adapting it to test also for
'articulation-type one can make it strip only specific articulations.
(haven't tested)

In my acutual use case (I haven't described well enough) the score
definitions are shared between score and parts (without and with bowings)
respectively. Maybe using tags one can achieve that one of them has
bowings while the other not.

 Another approach that might work is to put the articulations in a
 different music variable attached to spacers (e.g. “s1”) and then put
 it in simultaneous music like \yourMusic \yourBowings, but I
 can’t say much about that because I don’t do it.

This should also be possible. But I'd like to keep the bowings close
to the notes. On the other hand using this approach to would be possible
to have different sets of bowings. (Each orchestra might have different
preferences.)

Felix

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Color and/or parenthesize single dots in fret-diagrams (issue 102450043 by thomasmorle...@gmail.com)

2014-06-15 Thread marc 

Hi Harm,

great work, mostly LGTM, just two small nitpicks.


https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):

https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm#newcode119
scm/fret-diagrams.scm:119: ;; parantheses
typo: parentheses or -is

https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm#newcode1096
scm/fret-diagrams.scm:1096: The values for @var{string-number},
@var{fret-number}, and @var{finger}
This description is not precise IMHO. The first values have to be in
that order.
Do I have to code a value for finger before I use one ore more of the
optional arguments?
Would (place-fret 1 1 parenthesized) work?

https://codereview.appspot.com/102450043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Color and/or parenthesize single dots in fret-diagrams (issue 102450043 by thomasmorle...@gmail.com)

2014-06-15 Thread thomasmorley65 

On 2014/06/14 18:48:14, J_lowe wrote:

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

Documentation/notation/fretted-strings.itely:1002: color.
We need a new (obvious) paragraph for this new text I think, so give a

line

space after the previous one.



The syntax is a bit uncomfortable I think. Are they really just called

'dots'?


Here's my suggestion:



Fingering indication dots can be colored as well as parenthesized;

the

parenthesis's color can also be altered independently.



The example will show the subtleties of 'inversion' and

'modification'.

done

I highly appreciate any suggestion to improve my wording, syntax and
grammar...
Sometimes I feel it's more difficult to write documentation than code.

https://codereview.appspot.com/102450043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Color and/or parenthesize single dots in fret-diagrams (issue 102450043 by thomasmorle...@gmail.com)

2014-06-15 Thread thomasmorley65 

On 2014/06/15 07:46:22, marc wrote:

Hi Harm,



great work, mostly LGTM, just two small nitpicks.



https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):



https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm#newcode119

scm/fret-diagrams.scm:119: ;; parantheses
typo: parentheses or -is


done


https://codereview.appspot.com/102450043/diff/1/scm/fret-diagrams.scm#newcode1096

scm/fret-diagrams.scm:1096: The values for @var{string-number},
@var{fret-number}, and @var{finger}
This description is not precise IMHO. The first values have to be in

that order.

Hope it's better now.


Do I have to code a value for finger before I use one ore more of the

optional

arguments?


no


Would (place-fret 1 1 parenthesized) work?


yes, it will work



https://codereview.appspot.com/102450043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel