Dear Tim,
On 26.04.2013, at 19:28, Tim Roberts wrote:
> For the most part, it doesn't really matter. Both of the images you
> showed us are acceptable musically, so there's no real "right" or
> "wrong".
I beg to differ. What does "acceptable musically" imply - a musician with
suitable expertis
Stefan Vollmar nf.mpg.de> writes:
> \override Score.RehearsalMark #'extra-spacing-width = #'(-1 . 1)
> \override Score.RehearsalMark #'padding = #1.5
> ...
> \mark \default
> \grace s1
> \tempo "Moderato" 4 = 120
>
> I also needed the "extra-spacing-width", the "padding" and (curiously)
> the
Stefan Vollmar wrote:
> I also needed the "extra-spacing-width", the "padding" and (curiously) the
> "\grace s1" - I found the latter in an older thread of this list. I have
> attached screenshots with and without the additional lines before \tempo. But
> is this actually the "approved way" of g
Dear David,
On 22.04.2013, at 09:29, David Kastrup wrote:
>> why not just write
>
> \tempo "Allegro" 4 = 150
>
> and have the default formatting?
many thanks for the tip!
However, it turns out that this is not enough to circumvent the "stacking"
problem - but something like this works beau
Stefan Vollmar writes:
> Hallo,
>
> I have attached two screenshots to document the kind of layout problem I have
> with this snippet:
>
> [...]
> \time 3/4
> \mark \default % here: "L"
> \tempo 4 = 155
> \mm "Allegro" a2 f4
> d2 bes'4
> a2.\( [...]
>
> where
>
> mm =
> #(define-music-function
Hallo,
I have attached two screenshots to document the kind of layout problem I have
with this snippet:
[...]
\time 3/4
\mark \default % here: "L"
\tempo 4 = 155
\mm "Allegro" a2 f4
d2 bes'4
a2.\( [...]
where
mm =
#(define-music-function
(parser location tempotext)
(string?)
#{
