Craig Dabelstein writes:
> Hi all,
>
> Is it possible to store movement titles as a variable? e.g.,
>
> movtI = { \markup{I. Allegro} }
> movtII = { \markup{II. Adagio} }
>
> \header{
> piece = \movtI
> }
>
> So far I haven't been able to get this to work. Any ideas?
At 14:35 01/04/2018 +1000, Craig Dabelstein wrote:
Is it possible to store movement titles as a variable? e.g.,
movtI = { \markup{I. Allegro} }
movtII = { \markup{II. Adagio} }
\header{
piece = \movtI
}
So far I haven't been able to get this to work. Any ideas?
Is there any reason why you
Paul,
I compiled
\version "2.19.80"
\relative c'' {
g2 (\pitchedTrill a) \startTrillSpan bes
r4\stopTrillSpan }
No warning! Check the version you are using.
Mark
-Original Message-
From: Paul Scott [mailto:waterho...@ultrasw.com]
Sent: Saturday, March 31, 2018 6:20 PM
To: Mark
Hi all,
Is it possible to store movement titles as a variable? e.g.,
movtI = { \markup{I. Allegro} }
movtII = { \markup{II. Adagio} }
\header{
piece = \movtI
}
So far I haven't been able to get this to work. Any ideas?
Craig
--
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
On Fri, Mar 30, 2018 at 08:10:46PM -0700, Mark Stephen Mrotek wrote:
> Paul,
>
> See the attached snippet.
> Is it what you want?
Yes. That's a little embarrassing but what I need to accomplish has more to
it.
When I add a slur from a previous note:
\relative c'' {
g2( \pitchedTrill a)
On 31.03.2018 11:53, andrew.bern...@gmail.com wrote:
It’s not very _/semantic/_ hijacking the instrument name
If you want it more semantic, use a normal \header {} block, change
bookTitleMarkup and scoreTitleMarkup to no longer use the fields and
instead use \markup \fromproperty
On 31.03.2018 03:34, Andrew Bernard wrote:
What is the preferred way of putting a title for a movement to the
left of the start of the first system for a keyboard piece, that is,
in the space normally used for the indent?
Just in case: Of course you can use the instrumentName of a StaffGroup
Hello Harm,
Thanks for your help and thanks a lot to David for supplying this useful Scheme
code. I’ll use that for sure!
JM
> Le 31 mars 2018 à 16:16, Thomas Morley a écrit :
>
> 2018-03-30 18:25 GMT+02:00 Menu Jacques
Andrew,
You are welcome.
Such “hijackings” make this list so worthwhile!
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of andrew.bern...@gmail.com
Sent: Saturday, March 31, 2018 2:53 AM
To: lilypond-user@gnu.org
Subject: RE: Movement
2018-03-30 18:25 GMT+02:00 Menu Jacques :
> Hello,
>
> I’ve nearly reached my goal. Further attempts lead me to the following, using
> a GrandStaff and:
>
> \override GrandStaff.SpanBar.glyph-name = "|"
> \override Staff.BarLine.glyph-name = "'"
>
> I can’t
Hi Mark,
Thanks. I suspected as much. It’s not very _semantic_ hijacking the instrument
name (partly because it makes this concept hard to look up in the docs or
searches), but it does not matter.
Andrew
___
lilypond-user mailing list
Simon Albrecht writes:
> Hello everybody,
>
> it is currently not possible to tweak individual BassFigures – this:
>
> \version "2.19.80"
> \figures {
> <\single \hide BassFigure 6 3>
> }
>
> gives a
>
> syntax error, unexpected MUSIC_FUNCTION.
>
> How fundamental are
Am 31.03.2018 um 00:17 schrieb Simon Albrecht:
Hello everybody,
it is currently not possible to tweak individual BassFigures – this:
\version "2.19.80"
\figures {
<\single \hide BassFigure 6 3>
}
gives a
syntax error, unexpected MUSIC_FUNCTION.
How fundamental are the reasons for this?
13 matches
Mail list logo