Re: Parenthesised articulations
Kieren MacMillan writes:
> Hi David,
>
>> To LilyPond, braces indicate sequential music.
>
> Well, clearly there’s more going on than simply “sequential music”, or else
>
> \transpose c c’ { c d }
>
> would be no different than
>
> \transpose c c’ { c } d
>
> which clearly isn’t true.
It clearly isn't true. Also it is a non-sequitur. \transpose, like
many music functions, takes one music expression. Which can be a
sequential music expression, even an empty one (which is still an
expression of type SequentialMusic, just one with () as its elements
field).
>> Of course it sees the subsequent braces and acts according to their
>> meaning
>
> Then there’s no technical reason why my suggestion couldn’t work.
> That’s all I asked.
Shrug. You'll find that convincing LilyPond is not as easy as
convincing yourself. It's not particularly susceptible to syllogisms.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Hi David,
> To LilyPond, braces indicate sequential music.
Well, clearly there’s more going on than simply “sequential music”, or else
\transpose c c’ { c d }
would be no different than
\transpose c c’ { c } d
which clearly isn’t true.
> Of course it sees the subsequent braces and acts according to their meaning
Then there’s no technical reason why my suggestion couldn’t work.
That’s all I asked.
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Kieren MacMillan writes:
> Hi David,
>
>> { ^.^> } is equivalent to \sequential { ^.^> } which neither makes sense nor
>> works.
>
> Well, as a function,
>
>\parenthesize { ^.^> }
>
> makes total sense to me,
That's your privilege. To LilyPond, braces indicate sequential music.
> So are you saying that there’s some technical reason
>
> -\tweak parenthesize
>
> can’t “see” the subsequent braces and act accordingly?
No, I'm not saying anything of that kind. Of course it sees the
subsequent braces and acts according to their meaning, resulting in the
error messages you'll see when you try this.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Hi David,
> { ^.^> } is equivalent to \sequential { ^.^> } which neither makes sense nor
> works.
Well, as a function,
\parenthesize { ^.^> }
makes total sense to me, and is quite different from
\parenthesize ^. ^>
So are you saying that there’s some technical reason
-\tweak parenthesize
can’t “see” the subsequent braces and act accordingly?
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Kieren MacMillan writes:
> Hi David (et al.),
>
>> { 4-\tweak parenthesize #'a ^.-\tweak parenthesize #'a ^> }
>>
>> I'm not saying that this is supposed to be the last word on the
>> interface but it would produce the data I've been thinking of.
>
> This syntax has more flexibility than the more obvious/intuitive
>
> 4-\tweak parenthesize { ^.^> }
>
> That being said, is this version technically difficult/impossible?
> Just curious.
{ ^.^> } is equivalent to \sequential { ^.^> } which neither makes sense
nor works.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Hi David (et al.),
> { 4-\tweak parenthesize #'a ^.-\tweak parenthesize #'a ^> }
>
> I'm not saying that this is supposed to be the last word on the
> interface but it would produce the data I've been thinking of.
This syntax has more flexibility than the more obvious/intuitive
4-\tweak parenthesize { ^.^> }
That being said, is this version technically difficult/impossible?
Just curious.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Simon Albrecht writes:
> On 01.02.2016 11:38, David Kastrup wrote:
>> The "parenthesize" property is a boolean. Maybe it should be a
>> boolean-or-symbol ? And if it's a symbol, the respective engraver
>> collects all articulations with the same symbol and then sets one set of
>> parentheses around all of them?
>
> I can’t quite figure out what you mean. Could you give the pseudo-code
> version of
> { 4^.^> }
> with your suggested method?
{ 4-\tweak parenthesize #'a ^.-\tweak parenthesize #'a ^> }
I'm not saying that this is supposed to be the last word on the
interface but it would produce the data I've been thinking of.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
On 01.02.2016 11:38, David Kastrup wrote:
The "parenthesize" property is a boolean. Maybe it should be a
boolean-or-symbol ? And if it's a symbol, the respective engraver
collects all articulations with the same symbol and then sets one set of
parentheses around all of them?
I can’t quite figure out what you mean. Could you give the pseudo-code
version of
{ 4^.^> }
with your suggested method?
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Andrew Bernard writes: > Thanks Simon. Perfect. I also sometimes have trouble coming up with > names for these things! The "parenthesize" property is a boolean. Maybe it should be a boolean-or-symbol ? And if it's a symbol, the respective engraver collects all articulations with the same symbol and then sets one set of parentheses around all of them? I think we had the request for one paren around several elements a few times already. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
Thanks Simon. Perfect. I also sometimes have trouble coming up with names for these things! Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
On 31.01.2016 15:02, Simon Albrecht wrote:
shortAccentWithParens = -\tweak stencil #ly:text-interface::print
-\tweak text \markup {
Actually, each of the dashes before \tweak may be omitted.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Parenthesised articulations
On 31.01.2016 14:48, Andrew Bernard wrote:
If I have an accent and a staccato indication together on a note and I
want a single set of parentheses around both, how can this be
achieved? Is this possible?
How about that? Couldn’t think of a less clumsy name.
%%
\version "2.19.35"
shortAccentWithParens = -\tweak stencil #ly:text-interface::print
-\tweak text \markup {
\parenthesize
\put-adjacent #Y #DOWN
\musicglyph #"scripts.sforzato"
\musicglyph #"scripts.staccato"
}
->
{
c''^\shortAccentWithParens
}
%%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Parenthesised articulations
If I have an accent and a staccato indication together on a note and I want a
single set of parentheses around both, how can this be achieved? Is this
possible?
Andrew
— snip
% This does not achieve it.
\version "2.19.35"
{
c''^. -\parenthesize ^>
}
— snip
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
