> On 14 Jul 2019, at 00:30, Jacques Menu wrote:
>
> Hello Robin,
>
> Thanks, the result is already better, with the seconda volta at the right
> place after adjusting the parameter of \pseudoIndent.
>
> Didn’t find a way to hide the empty part of the staff to the left of it,
> stopStaff/start
Hi Jacques,
Am So., 14. Juli 2019 um 01:30 Uhr schrieb Jacques Menu :
>
> Hello Robin,
>
> Thanks, the result is already better, with the seconda volta at the right
> place after adjusting the parameter of \pseudoIndent.
>
> Didn’t find a way to hide the empty part of the staff to the left of it
Jacques Menu wrote:
Didn’t find a way to hide the empty part of the staff to the left of it,
stopStaff/startStaff didn’t help.
Sorry.
This simplistic pseudoIndent is too fragile for general use.
It needs to be made robust re vertical extents.
In your case you need a LeftEdge.Y-offset of -4
Hi list,
I’m currently working on a patch that would make the default ottavation
texts/markups (currently "8va"/"15ma" and "8vb"/"15mb") changeable by
the user without having to \set Staff.ottavation after each \ottava, see
the following code and attached picture:
%%%
This score gives a strange result (uses open string for the b and the e).
>
\version "2.19.81"
\language "english"
\new TabStaff {
\set TabStaff.minimumFret = #3
\relative c' {}
}
>
Am I doing something wrong? Is there a way to fix this?
Immanuel
tmp.pdf
Description: Adobe PDF document
Am 14.07.19 um 12:42 schrieb Immanuel Litzroth:
Am I doing something wrong? Is there a way to fix this?
minimum-fret allows open strings because you don’t need the left hand
for them. You can disallow that behaviour:
\set TabStaff.restrainOpenStrings = ##t
Thanks,
I also found that indicating string numbers works.
Immanuel
On Sun, Jul 14, 2019 at 12:53 PM Malte Meyn wrote:
>
>
> Am 14.07.19 um 12:42 schrieb Immanuel Litzroth:
> > Am I doing something wrong? Is there a way to fix this?
>
> minimum-fret allows open strings because you don’t need the
Hi Malte,
Well this is interesting. What you have shown is perfectly normal in
many editions. Some editions line up the dash with the top of the va
abbrev., and some on the baseline, and some in the middle. It's a matter
of personal taste. Trying to force one way of typesetting is not in the
On 12.07.19 20:04, Werner LEMBERG wrote:
Functions like transpose act destructively on their argument, so you
need a copy or the original will get changed. [...]
How can Joe User find out whether a function is acting destructively?
The Extending Manual tells him about using $ in music functi
From: Immanuel Litzroth
Date: Sunday, July 14, 2019 at 4:42 AM
To:
Subject: tabstaff minimumfret behaving badly
This score gives a strange result (uses open string for the b and the e).
>
\version "2.19.81"
\language "english"
\new TabStaff {
\set TabStaff.minimumFret = #3
\relative c' {}
Malte Meyn wrote:
How can this made be top- or bottom-aligned (or aligned depending
according to the 'direction property)?
Inside a #(define-markup-command (command-name layout props arg1 arg2 …)
you can collect 'direction as follows:
(let* ((dir-prop (chain-assoc-get 'direction props 1)))
Oh dear, that recommendation was for your first code.
The bass clef code needs a LeftEdge.Y-offset of -5
Cheers,
Robin
On 14.07.2019 12:10, Robin Bannister wrote:
Jacques Menu wrote:
Didn’t find a way to hide the empty part of the staff to the left of it,
stopStaff/startStaff didn’t help.
Am 14.07.19 um 13:15 schrieb Andrew Bernard:
Provide the mechanism, sure, but don't prescribe a single appearance. I
don't even think there is a default that would suit everybody, that's
the point.
Of course I wouldn’t change LilyPond’s default. The markups I showed
would be only an example
Am 14.07.19 um 16:21 schrieb Robin Bannister:
Malte Meyn wrote:
How can this made be top- or bottom-aligned (or aligned depending
according to the 'direction property)?
Inside a #(define-markup-command (command-name layout props arg1 arg2 …)
you can collect 'direction as follows:
(let*
Malte Meyn wrote:
#{ \markup \concat \general-align #Y #UP { "16" \teeny "ma" } #}
works but
(markup #:concat #:general-align Y UP ("16" #:teeny "ma"))
doesn’t and I don’t know why …
One explanation is that
- concat wants to be given (markup-list?)
- general-align wants to
Robin Bannister wrote:
One explanation is that
- concat wants to be given (markup-list?)
- general-align wants to be given (markup?)
So the two should be swapped:
#(markup #:general-align Y UP #:concat ("16" #:teeny "ma"))
This of course implies that your #{ #} version shouldn't
Am 15.07.19 um 08:12 schrieb Robin Bannister:
It is normal 'automagic' for
\box { "X" "Y" "Z"}
to be mapped into
{ \box "X" \box "Y" \box "Z" }
giving you 3 boxes in a markup list
to which \concat can be applied.
Seems like that magic happens only for LilyPond syntax markups.
The ma
17 matches
Mail list logo
