On Feb 6, 2018, at 20:44, nine.fierce.ball...@gmail.com wrote:
>
> Reviewers: ,
>
> Message:
> I would be happy to hear suggestions for the name of this command.
Esteemed LilyPond developers,
Thank you for the voluminous feedback. It is encouraging to hear that a
solution using unique IDs wou
On 07.02.2018 10:37, Torsten Hämmerle wrote:
So why not using something like *\repeatMark*, *\markRepeat* or
*\markRepetition*, ...?
Seen that way, even \repeatMark "Fine" feels natural to me, because - like
an ordinary RehearsalMark, or a MetronomeMark, it's just a new kind of Mark,
which is, wi
Werner LEMBERG writes:
>>> If we want to capture semantics properly, I believe we need to
>>> recognize that there are three different kinds of marks:
>>>
>>> 1) "jump-from" marks (D.S. al ..., D.C. al ..., To Coda)
>>> 2) "jump-to" marks (Segno, beginning of piece, coda)
>>> 3) "stop playing" ma
>> If we want to capture semantics properly, I believe we need to
>> recognize that there are three different kinds of marks:
>>
>> 1) "jump-from" marks (D.S. al ..., D.C. al ..., To Coda)
>> 2) "jump-to" marks (Segno, beginning of piece, coda)
>> 3) "stop playing" marks (Fine, end of piece) [...]
Flaming Hakama by Elaine wrote:
In rehearsals, at least in the US, going over these markings is called
going over the roadmap.
Well, Diverge and Merge are the terms used by road (freeway) engineers.
Cheers,
Robin
___
lilypond-devel mailing list
l
Carl Sorensen writes:
> For me, it's not the Italian part, it's the "musical" part, that is,
> what do I see when I read the music. The fact that it is Italian is
> secondary. That being said, the \fine command is a bit weird, because
> it could be confused with the English word "fine" meaning
-- Forwarded message --
From: Carl Sorensen
To: Kieren MacMillan
Cc: "Torsten Hämmerle" , "lilypond-devel@gnu.org"
Bcc:
Date: Wed, 7 Feb 2018 16:02:50 +
Subject: Re: Issue 5272: Add \depart (issue 337520043 by
nine.fierce.ball...@gmail.com)
On 2/7/18, 8:55 AM, "Kieren Mac
Hi Carl
I can't resist adding my tuppence-worth :)
You wrote 07/02/2018 15:18:55
If we want to capture semantics properly, I believe we need to
recognize that there are three different kinds of marks:
1) "jump-from" marks (D.S. al ..., D.C. al ..., To Coda)
2) "jump-to" marks (Segno, beginni
On 2/7/18, 9:05 AM, "David Kastrup" wrote:
Carl Sorensen writes:
> On 2/7/18, 2:37 AM, "lilypond-devel on behalf of Torsten Hämmerle"
wrote:
>
>
> If there will probably even be a MIDI playback in the future, we
actually
> need "real" marks to jump to,
Carl Sorensen writes:
> On 2/7/18, 2:37 AM, "lilypond-devel on behalf of Torsten Hämmerle"
> torsten.haemme...@web.de> wrote:
>
>
> If there will probably even be a MIDI playback in the future, we actually
> need "real" marks to jump to, not only text markups.
> This being said, I'
On 2/7/18, 8:55 AM, "Kieren MacMillan" wrote:
Hi Carl,
Of all suggestions so far, I most like your flow/Flow the most.
> If we want to capture semantics properly, I believe we need to recognize
that there are three different kinds of marks:
> 1) "jump-from" marks (D.
Hi Carl,
Of all suggestions so far, I most like your flow/Flow the most.
> If we want to capture semantics properly, I believe we need to recognize that
> there are three different kinds of marks:
> 1) "jump-from" marks (D.S. al ..., D.C. al ..., To Coda)
> 2) "jump-to" marks (Segno, beginning o
On 2/7/18, 2:37 AM, "lilypond-devel on behalf of Torsten Hämmerle"
wrote:
If there will probably even be a MIDI playback in the future, we actually
need "real" marks to jump to, not only text markups.
This being said, I'd favour *something containing "mark" and "repeat"*,
bec
(new here because gmane is dud)
This is a signpost at a fork in the road.
I propose ForkMark
This concerns junctions where you can diverge off the one-way main road.
I don't experience merging junctions, e.g. Segno, as forks.
So saying DivergeMark would be unneccessarily explict -
unless
Reviewers: Malte Meyn,
Message:
On 2018/02/07 07:41:09, Malte Meyn wrote:
“Make […] work for *me*” sounds as if this isn’t a general problem? I
don’t know
*anything* about emacs (except that vim is superior :P) but googling
c-default-style makes me wonder whether this isn’t only a problem of
How about \flow and FlowScript?
Carl
Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
\location or \place, with LocationMark or PlaceMark to match?
\location sounds excellent.
https://codereview.appspot.com/337520043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2018/02/07 06:34:32, lemzwerg wrote:
Very nice idea!
> On the other hand, \goTo seems unlikely to resemble whatever
> we settle on for the grob name… unless everyone likes GoToScript.
What about \jumpTo? Note that I like \goTo also, and I don't mind if
the
low-level stuff uses `depart
Hello all,
Admittedly, something like "goto" or "jump" seemed obvious to me, too.
In more musical terms, however, we're talking about "repeated sections". As
opposed to repeat bars, there are textual instructions involved, and there
are, sort of, "marks" involved, too: capo, fine, segno, etc.
If
19 matches
Mail list logo
