Erik Appeldoorn wrote Saturday, October 31, 2009 11:48 PM
% make note heads smaller
\set fontSize = #-4
^^
I did forget to type the \set but the result is still the same.
Did you remember to remove the \?
Trevor
___
lilypond-user mailin
Hi Erik,
I did forget to type the \set but the result is still the same…
When you are changing the font size within a music expression, you
use the command \set fontSize.
When you are changing the font size within a \context definition
block, you simply use fontSize (i.e., no \set, and not \
According to the manual:
3.3.4 Modifying context properties
fontSize Real Increase or decrease the font size
and further:
% make note heads smaller
\set fontSize = #-4
I did forget to type the \set but the result is still the same
Erik
_
From: James E. Bailey [ma
If I remember correctly, \fontSize is not a known LilyPond string.
On 01.11.2009, at 00:20, Erik Appeldoorn wrote:
Why do I get ëscaped string” error here. The compiled result looks
ok to me
\layout {
\context {
\Staff
\override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 3)
Why do I get ëscaped string error here. The compiled result looks ok to me
\layout {
\context {
\Staff
\override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 3)
\fontSize = #-2
}
}
Hou je goed / Keep well,
Erik
___
lil
David Pounder schrieb:
--- Original Message ---
From: Kieren MacMillan
To: David Pounder
Sent: 25.10.09, 13:28:05
Subject: Re: Codas / Trios
Hi David,
The ideal solution would be for da capo, dal segno and codas to be
handled (somehow) by the \repeat and \unfoldRepeats constr
Hi,
I have a question about accessing information about several related grobs at
once. For example, if I wanted to use information about a beam and a tuplet
number positioned above it in a single procedure, where would these grobs be
associated together, and how could I refer to them in turn?
Th
Marc Hohl schrieb:
Hello,
how can a snippet in the LSR be corrected?
http://lsr.dsi.unimi.it/LSR/Snippet?id=633
is not perfect, it should look like
---[snip]---
%LSR Contributed by Frederico Bruni
%% Hide fret number: useful to draw slide into/from a casual point of
%% the fretboard.
hideFr
Hello,
how can a snippet in the LSR be corrected?
http://lsr.dsi.unimi.it/LSR/Snippet?id=633
is not perfect, it should look like
---[snip]---
%LSR Contributed by Frederico Bruni
%% Hide fret number: useful to draw slide into/from a casual point of
%% the fretboard.
hideFretNumber = { \once \
Graham Percival schrieb:
On Sat, Oct 31, 2009 at 09:31:19AM +0100, Marc Hohl wrote:
Sorry - I wanted to tweak it, but I was busy and finally forgot.
I have added a function which takes care of glissandi between
two equal note head positions. If I can manage to automatically
take the accident
2009/10/31 Graham Percival :
> And do you have any
> idea why there's so many clashing note columns? Is that a normal
> message for tab stuff?
It's a grace note bug. The upper voice has \voiceOne set, but it's
ignored following the first acciaccatura.
Regards,
Neil
___
On Thu, Oct 29, 2009 at 02:59:39PM +0200, Reinhold Kainhofer wrote:
> 2) look up the manual, which takes a few seconds, since a) their title is not
> bold, b) the same size as the other text and c) it is written in green, which
> makes even less contrast than the black text on the green backgroun
Quoting Bertalan Fodor :
But in 4/4 with partial? I don't have access to lily now but i think
i saw that failing.
It should still not be centered, should it? The bug/limitation you
might have in mind is that you have to play some tricks to make
\RemoveEmptyStaffContext remove a line that onl
On Thu, Oct 29, 2009 at 01:44:54AM +0100, James E. Bailey wrote:
>On 29.10.2009, at 00:40, Graham Percival wrote:
>
> I suppose that I'm dealing with release issues at the moment, but
> I think the python thing comes from the lilypad package
> generation. Hmm, perhaps now that
On Sat, Oct 31, 2009 at 09:31:19AM +0100, Marc Hohl wrote:
> Sorry - I wanted to tweak it, but I was busy and finally forgot.
>
> I have added a function which takes care of glissandi between
> two equal note head positions. If I can manage to automatically
> take the accidentals into account, this
Le 31 oct. 2009 à 12:40, Jiri Zurek (Prague) a écrit :
However, since the variant may at times span accross several (2-3)
lines of music, I needed that there may be multi-line score
fragments inside
the markuplines.
At the moment, you won't be able to have:
Some text with =short=score= a
The
http://old.nabble.com/Inline-score-inside-markup---bugs-in-music-alignment-td26111727.html
lengthy discussion with David Kastrup about the mixing pieces of text with
fragments of score inside a markuplines block (by the way, I am still
waiting for a solution at that thread - although we have
how to code a tail-recursive version of this.
#(define (draw hole nbends)
(define bend-glyphs "")
(while
(> nbends 0)
(set! bend-glyphs (markup #:flat bend-glyphs))
(set! nbends (1- nbends)))
(markup bend-glyphs #:circle hole))
Perhaps something like that ? :
#(define (draw hole nb
Graham Percival schrieb:
On Tue, Oct 27, 2009 at 12:01:24PM +0100, Federico Bruni wrote:
Unfortunately, I haven't figured out how to add the tweaks suggested by
Graham.
So if someone else is able to do it, he's free to emprove the (attached)
file (read the TODO section in the beginning).
> I just checked Honegger's score for Jeanne d'Arc and tempo marks are above
> the top staff and then below for the strings. I've looked in the manual 2.12
> and snippets and I don't see a way to do this.
> I tried setting it for the top instrument in each group and that did not work.
The attac
20 matches
Mail list logo