In message <4b7bcbfe.80...@hulin.org.uk>, Ian Hulin
writes
\score {
\header {
title = "Trio"
}
% Music for Section B of Scherzo, aka Trio, ending with
% "Da Capo" type markup
}
\score {
\header {
title = "Coda" % or \mar
In message <4b79c831.7080...@hulin.org.uk>, Ian Hulin
writes
On 15/02/10 18:47, David Pounder wrote:
Dal Segno Al Coda
A "§" B C "©" D "Dal Segno al Coda" E ==> A B C D B C E
Firstly, can anyone think of any more combinations I may have missed here?
To Trio.
Thanks for that, David,
On 16/02/10 17:20, reinhold [via LilyPond Frogs] wrote:
Am Dienstag, 16. Februar 2010 18:07:11 schrieb Ian Hulin:
> Kieren MacMillan wrote:
> > Hi all,
> >
> > I've been lurking a bit on this thread, but felt I should comment.
> >
> > I personally think we need a more general structure than \rep
Marc Hohl writes:
> David Kastrup schrieb:
>
>> But the point is that "repeat volta" and "coda" and whatever else in
>> the music list should be just interesting for the grob engraver, and
>> performer and repeat unfolder and cautionaries and stuff get their
>> info from a lower-level primitive d
David Kastrup schrieb:
Marc Hohl writes:
After reading through the other posts, I think that overloading
\repeat would not cover *all* possible
cases. On the other hand, there should be *one* consistent way of
doing any kind of repeats.
David's comparison with goto-like structures seems to
Marc Hohl writes:
> After reading through the other posts, I think that overloading
> \repeat would not cover *all* possible
> cases. On the other hand, there should be *one* consistent way of
> doing any kind of repeats.
>
> David's comparison with goto-like structures seems to be the right
> ap
Ian Hulin schrieb:
Hi Marc,
On 15/02/10 18:32, Marc Hohl wrote:
Ian Hulin schrieb:
[...]
Secondly, what I had in mind was this kind of thing:
* \dalsegno and \dacapo - both of these start off a segno/dacapo
section. I know it's a bit weird that the \dacapo command would
have
Hi David,
Excellent points -- in particular:
> Those "goto" and "function calls" should be able to have some basic
> effects not just on performance, but also on typesetting: ties starting
> before a branch point (or function return) need to be ended in each
> branch, the same for slurs and so on
Kieren MacMillan writes:
> Hi all,
>
> I've been lurking a bit on this thread, but felt I should comment.
>
> I personally think we need a more general structure than \repeat will
> ever be able to reasonably offer.
My take on this is that we need the equivalent of (multiple) "goto" and
function
Hi all,
I've been lurking a bit on this thread, but felt I should comment.
I personally think we need a more general structure than \repeat will ever be
able to reasonably offer. Essentially, we need to be able to say that a single
movement/piece [of Lilypond code] consists of one or more \sect
Hi David,
On 16/02/10 07:00, David Pounder wrote:
--- Original Message ---
From: Ian Hulin
To: David Pounder
Sent: 15.2.10, 22:18:25
Subject: Re: [frogs] Da Capos, Codas and Segnos
On 15/02/10 18:47, David Pounder wrote:
--- Original Message ---
From: Ian Hulin
"David Pounder" writes:
>> --- Original Message ---
>> From: Ian Hulin
>> To: David Pounder
>
> Apologies for the blank replies - my e-mail client has been playing
> up.
While you are at it: could you _please_ cut out anything from your
article quotes that is not relevant to your reply
Marc Hohl writes:
> I have also thought about implementing this properly.
>
> I had the idea to extend the \repeat syntax:
>
> \repeat segno {.A.}
> \alternative {{ .B. }{ .C.}}
That appears quite preferable to me. One problem I see is that there
sometimes is a number of repeat structures. An
> --- Original Message ---
> From: Ian Hulin
> To: David Pounder
> Sent: 15.2.10, 22:18:25
> Subject: Re: [frogs] Da Capos, Codas and Segnos
>
> On 15/02/10 18:47, David Pounder wrote:
> >
> >
> >> --- Original Message ---
> &g
Regards,
David Pounder
> --- Original Message ---
> From: Ian Hulin
> To: David Pounder
> Sent: 15.2.10, 22:18:25
> Subject: Re: [frogs] Da Capos, Codas and Segnos
>
> On 15/02/10 18:47, David Pounder wrote:
> >
> >
> >> --- Ori
Hi Marc,
On 15/02/10 18:32, Marc Hohl wrote:
Ian Hulin schrieb:
[...]
Secondly, what I had in mind was this kind of thing:
* \dalsegno and \dacapo - both of these start off a segno/dacapo
section. I know it's a bit weird that the \dacapo command would
have to be at the start
On 15/02/10 18:47, David Pounder wrote:
--- Original Message ---
From: Ian Hulin
To: Lilypond Frogs List
Sent: 15.2.10, 17:40:48
Subject: [frogs] Da Capos, Codas and Segnos
Hi Frogs and Developers,
This is by way of limbering up for a discussion on the GLISS list when
it gets
> --- Original Message ---
> From: Ian Hulin
> To: Lilypond Frogs List
> Sent: 15.2.10, 17:40:48
> Subject: [frogs] Da Capos, Codas and Segnos
>
> Hi Frogs and Developers,
> This is by way of limbering up for a discussion on the GLISS list when
> it get
Regards,
David Pounder
> --- Original Message ---
> From: Ian Hulin
> To: Lilypond Frogs List
> Sent: 15.2.10, 17:40:48
> Subject: [frogs] Da Capos, Codas and Segnos
>
> Hi Frogs and Developers,
> This is by way of limbering up for a discussion on the GL
Ian Hulin schrieb:
[...]
Secondly, what I had in mind was this kind of thing:
* \dalsegno and \dacapo - both of these start off a segno/dacapo
section. I know it's a bit weird that the \dacapo command would
have to be at the start of the score, but I think it would be
ben
Hi Frogs and Developers,
This is by way of limbering up for a discussion on the GLISS list when
it gets going.
I'm trying to think of all the commoner combinations of Segnos, Codas
and Da Capo instructions so maybe we can work out a consistent syntax
for addressing what are, after all, variat
21 matches
Mail list logo
