I'm trying to define a markup function for establishing a common set of
formatting for a number of text markups.
%%% beginning of sample code
\version "2.19.82"
\displayScheme
\markup{\sans{\fontsize #10 "C"}} % Just used to show the scheme markup
command -- this is what I'm trying
#(defin
Carl Sorensen writes:
> I'm trying to define a markup function for establishing a common set of
> formatting for a number of text markups.
>
> %%% beginning of sample code
>
> \version "2.19.82"
>
> \displayScheme
> \markup{\sans{\fontsize #10 "C"}} % Just used to show the scheme markup
> comm
On 2019-01-17 6:27 am, Carl Sorensen wrote:
I'm trying to define a markup function for establishing a common set
of formatting for a number of text markups.
%%% beginning of sample code
\version "2.19.82"
\displayScheme
\markup{\sans{\fontsize #10 "C"}} % Just used to show the scheme
markup c
Dear list!
I’m all new to lily pond and trying to create a custom spanner (a couple of
parallel lines connecting some of the holes of two fingering charts). To
hack this together I would need the length of the spanner I’m modifying or
replacing. I’ve put this piece of code together to extract it a
On 2019-01-17 6:43 am, Leo Correia de Verdier wrote:
Dear list!
I’m all new to lily pond and trying to create a custom spanner (a
couple of
parallel lines connecting some of the holes of two fingering charts).
To
hack this together I would need the length of the spanner I’m modifying
or
repl
Aaron Hill wrote
> On 2019-01-16 5:24 pm, Reggie wrote:
>> First, are you saying that every time I want to manually adjust one
>> staff in
>> a system in one instance I must create a new voice just to hack this?
>> Like
>> you did? What about my original code itself used?
>
> You do not need the
I worked on your example, and here is the result.
The "\drop n" function drop the nth note from above, an can be nested
(to do drop 2 drop 4)
The funcion "\rise n" function rise the nth note from below, an can be
nested too
The "\inversion n" function do the inversions of the chord.
I'm su
Hi Evan,
Welcome to LilyPond!
On 1/15/19, 11:10 AM, "Evan Levine" wrote:
Good afternoon! I've got a few things I'm brewing right now, but the
most pressing is that I'm looking to set all of the chord diagrams for a
lead sheet at the top of the page under the title, and modify the
On 1/17/19, 8:02 AM, "David Kastrup" wrote:
>
> I've used displayScheme to get the representation of the markup
> function. I've found that is uses #:line so that I have to use
> make-line-markup.
#:sans is garbage outside of the markup macro. Also make-line-markup
Carl Sorensen writes:
> On 1/17/19, 8:02 AM, "David Kastrup" wrote:
>
> >
> > I've used displayScheme to get the representation of the markup
> > function. I've found that is uses #:line so that I have to use
> > make-line-markup.
>
> #:sans is garbage outside of the ma
On 1/17/19, Davide Bonetti wrote:
> I worked on your example, and here is the result.
Nice!
> I'm sure there is a better way to write the inversion function, but I
> haven't find a way to program the repetition of a function in scheme.
This is certainly not the most elegant way, but it seems to
Valentin Villenave writes:
> On 1/17/19, Davide Bonetti wrote:
>> I worked on your example, and here is the result.
>
> Nice!
>
>> I'm sure there is a better way to write the inversion function, but I
>> haven't find a way to program the repetition of a function in scheme.
>
> This is certainly
On 1/18/19, David Kastrup wrote:
> This is not really an issue for string-manipulation.
Agreed. Nevertheless, I was pleasantly surprised to see that
ly:parser-include-string could accept an incomplete expression.
(Previously, ly:parser-parse-string would have been much less flexible
here.)
> Let
Valentin Villenave writes:
> On 1/18/19, David Kastrup wrote:
>> This is not really an issue for string-manipulation.
>
> Agreed. Nevertheless, I was pleasantly surprised to see that
> ly:parser-include-string could accept an incomplete expression.
> (Previously, ly:parser-parse-string would hav
David Kastrup writes:
> Valentin Villenave writes:
>
>> On 1/18/19, David Kastrup wrote:
>>> This is not really an issue for string-manipulation.
>>
>> Agreed. Nevertheless, I was pleasantly surprised to see that
>> ly:parser-include-string could accept an incomplete expression.
>> (Previously,
Yet another annoying question about documentation from me.
After figuring out how to make a glissando longer, and discovering this in
the NR under the spanner interface:
minimum-length (dimension, in staff space)
Try to make a spanner at least this long, normally in the horizontal
direction. This
16 matches
Mail list logo
